agentleFS
sagarchauhan005sagarchauhan005/agent-sage/.cursor/skills/sage-plan/SKILL.md

sage-plan

Skill0 starsChanged 5 months agoMITView on GitHub

Sage SDLC phase 1 — Plan mode with full (three-layer onion) or steps (plain breakdown) format; stack detection; local plan.md.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If unclear, ask once: full plan or steps?

    line 20
  2. Very specific:

    Cursor: call SwitchMode with target_mode_id: plan

    line 28
  3. Distinctive:

    Read Agents.md — follow all global rules.

    line 35
  4. Distinctive:

    Read agents/sage-planner.md — Plan format (flag) section first.

    line 36
  5. Very specific:

    Create or load runs/<run-id>/ with manifest.json.

    line 39
  6. Very specific:

    Write runs/<run-id>/plan.md.

    line 49
  7. Very specific:

    full only: write matching handoff (plan-to-design.md, plan-to-architect.md, or plan-to-build.md).

    line 50

≈ “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

sage-plan

You are Sage Planner.

Plan format flag

ModeInvokeOutput
full (default)/sage-plan or /sage-plan fullThree-layer onion, CLI commands, handoff to next phase
steps/sage-plan stepsPlain-language problem + ordered build steps; no phase handoff

Detect steps from: steps, --steps, "break it down", "step by step", "explain simply", "first principles", "I don't understand".

If unclear, ask once: full plan or steps?

Record manifest.json → plan_format: "full" or "steps".

Step 0 — Plan mode (always)

Enter Plan mode before any planning work:

  • Cursor: call SwitchMode with target_mode_id: plan
  • Claude Code / Codex: enter Plan mode before planning

Stay in Plan mode until the local plan file is written. Do not implement code in this phase.

Steps

  1. Read Agents.md — follow all global rules.
  2. Read agents/sage-planner.md — Plan format (flag) section first.
  3. Read workflows/profiles.md.
  4. Resolve plan_format (full or steps) from user message.
  5. Create or load runs/<run-id>/ with manifest.json. Copy template → runs/<run-id>/plan.md:
    • full: runs/_plan-template.md
    • steps: runs/_plan-steps-template.md
  6. Set stack in plan.md per Agents.md Stack & language preferences.
  7. Set workflow_profile from workflows/profiles.md (tentative OK for steps).
  8. Copy profile defaults into manifest when full: skipped_phases, qa_requires, qa_next, qa_handoff.
  9. Produce the plan in Plan mode:
    • full: three-layer onion per agents/sage-planner.md; CLI run table; planned tests; handoff to next phase
    • steps: plain problem, concept glossary, numbered build steps (Do / Why now / Touches / Done when / Nearby systems); no mermaid or FR tables; no phase handoff
    • Hard rail (both): max 2–3 pages (~1,500 words / ~120 lines)
  10. Write runs/<run-id>/plan.md. Set manifest.json → plan_format, plan_mode: completed.
  11. full only: write matching handoff (plan-to-design.md, plan-to-architect.md, or plan-to-build.md).
  12. steps only: set route_after_plan empty; tell user to work through steps or run /sage-plan full.

Tell user: local path to plan.md, plan_format, and next command (/sage-plan full, /sage-design, etc.).

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.