agentleFS
loganware05loganware05/captains-compass-cursor/.cursor/skills/design-before-plan/SKILL.md

design-before-plan

Skill2 starsChanged 36 days agoMITView on GitHub

Use before creative or behavior-changing work — tease out approaches and a short design for Captain sign-off before writing IMPLEMENTATION_PLAN.md

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before /plan-feature / writing IMPLEMENTATION_PLAN.md

    line 15
  2. Distinctive:

    When the request already specifies everything that matters (e.g.

    line 19
  3. Distinctive:

    Look before you ask: Read referred files and related code until you can explain how things work today and what would change.

    line 31
  4. Distinctive:

    Ask the Captain to pick one (or amend).

    line 35
  5. Very specific:

    Get explicit design approval: before creating or updating IMPLEMENTATION_PLAN.md.

    line 38
  6. Very specific:

    After design approval, load Skill implementation-planning / run /plan-feature and produce the approval-gated plan as usual.

    line 40
  7. Distinctive:

    Do not skip the Captain plan-approval gate after design

    line 53
  8. Distinctive:

    Do not implement product files during design

    line 54
  9. Distinctive:

    Do not install third-party Superpowers/ECC plugins

    line 55
  10. Distinctive:

    Do not reopen decided Captain choices without new evidence

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Design Before Plan

Patterns inspired by obra/superpowers brainstorming (DISCOVERED inspiration — not a plugin install).

Use this Skill when

  • Creating features, changing product behavior, or non-trivial design choices
  • The request leaves approach, UX, or architecture open
  • Before /plan-feature / writing IMPLEMENTATION_PLAN.md

Skip (quick tasks)

When the request already specifies everything that matters (e.g. “rename X to Y”, “make the icon cornflower blue”), do the work under normal rules — do not force a design ceremony.

Inputs

  • Captain request
  • Existing project memory and relevant code/docs
  • Any prior decisions the Captain already made

Procedure

  1. Look before you ask. Read referred files and related code until you can explain how things work today and what would change. Do not re-ask what the repo or Captain already answered.
  2. Lay out approaches in their own message (2–3 realistic options, trade-offs). Ask the Captain to pick one (or amend).
  3. Write a short design (or fuller design doc for large work): goal, chosen approach, boundaries, non-goals, risks. Size to what a Captain can actually read.
  4. Get explicit design approval before creating or updating IMPLEMENTATION_PLAN.md.
  5. After design approval, load Skill implementation-planning / run /plan-feature and produce the approval-gated plan as usual.

Spikes the Captain explicitly approved are exploration only — still no product behavior ship without a later plan gate when implementation follows.

Output

  • Approaches + chosen design (Captain-approved)
  • Handoff into IMPLEMENTATION_PLAN.md (still AWAITING APPROVAL until plan gate)

Prohibited actions

  • Do not skip the Captain plan-approval gate after design
  • Do not implement product files during design
  • Do not install third-party Superpowers/ECC plugins
  • Do not reopen decided Captain choices without new evidence

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.