agentleFS
jsmastery-projsmastery-pro/jsm-hq/.agents/skills/plan/SKILL.md

plan

Skill102 starsChanged 34 days agoMITView on GitHub

Think through what you are about to build like a senior engineer before writing any code. Surfaces decisions, aligns on language, and produces a confirmed implementation plan before anything starts. Run this before every feature, every time.

184 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use heartmula, webhook-subscriptions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • math-incSkill

    heartmula

    Set up and run HeartMuLa, the open-source music generation model family (Suno-like). Generates full songs from lyrics + tags with multilingual support.

    Also in 9 projects that use this

  • Tommy-ywSkill

    webhook-subscriptions

    Create and manage webhook subscriptions for event-driven agent activation, or for direct push notifications (zero LLM cost). Use when the user wants external services to trigger agent runs OR push notifications to chats.

    Also in 5 projects that use this

  • math-incSkill

    minecraft-modpack-server

    Set up a modded Minecraft server from a CurseForge/Modrinth server pack zip. Covers NeoForge/Forge install, Java version, JVM tuning, firewall, LAN config, backups, and launch scripts.

    Also in 5 projects that use this

  • john-data-chenSkill

    touchdesigner-mcp

    Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.

    Also in 6 projects that use this

  • gaebalaiSkill

    codex-system

    PROACTIVELY consult Codex CLI, your highly capable supporter with exceptional reasoning and task completion abilities. Codex is a trusted expert you should ALWAYS consult BEFORE making decisions on: design choices, implementation approaches, debugging strategies, refactoring plans, or any non-trivial problem. When uncertain, consult Codex. Don't hesitate - Codex provides better analysis. Explicit triggers: "think deeper", "analyze", "second opinion", "consult codex".

    Also in 3 projects that use this

  • ibahgatSkill

    context-optimize

    Improve context efficiency and cache stability for long or complex sessions.

    Also in 3 projects that use this

  • +3 more from math-inc

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 14 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 14

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before saying anything, take stock of what already exists.

    line 30
  2. Distinctive:

    Read in this order:

    line 32
  3. Distinctive:

    Do not ask about anything already clearly answered by existing documentation.

    line 42
  4. Distinctive:

    Every project has its own vocabulary.

    line 48
  5. Distinctive:

    Update your understanding immediately if the developer corrects a term.

    line 64
  6. Distinctive:

    Ask one question at a time

    line 75
  7. Distinctive:

    If their answer makes another decision irrelevant — skip it

    line 78
  8. Distinctive:

    Stop when every decision that would change the implementation has been resolved.

    line 95
  9. Distinctive:

    When you are done, say:

    line 99
  10. Distinctive:

    After saying "Plan ready", write a clear implementation plan based on everything discussed.

    line 109
  11. Distinctive:

    Only after explicit confirmation does implementation begin.

    line 134
  12. Distinctive:

    After the developer confirms the plan, ask once:

    line 140
  13. Distinctive:

    Use the implementation plan content as the file body.

    line 158
  14. Distinctive:

    No file is written. No follow-up questions.

    line 173

“Common” is measured: kept by at least 6 in 10 of the 168 edited versions of this file we could read. “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

Project Context File

This skill reads and writes the project context file. The name depends on your tool:

  • Claude Code → CLAUDE.md
  • Cursor → .cursor/rules/rules.md
  • Codex → AGENTS.md
  • Windsurf → .windsurfrules
  • Other tools → check your tool's documentation

Throughout this skill, "project context file" refers to whichever file your tool uses.


You are a senior engineer sitting with a developer before they start building. Your job is not to interrogate them — it is to think alongside them. To ask the questions a senior engineer would ask before letting someone start coding. To catch the things that seem obvious but are not. To make sure both of you are building the same thing in your heads before either of you touches the code.

This is a thinking session. Not a grilling session.


Step 1 — Understand What's Here

Before saying anything, take stock of what already exists.

Read in this order:

  • The feature description the developer gave you
  • project context file if it exists — for project rules and stack
  • context/index.md if it exists — for current project state
  • context/blueprint.md if it exists — for architecture decisions
  • The relevant plan file in context/plans/ if one exists for this feature
  • Any existing code directly relevant to this feature

Build a clear picture of what needs to be built and what already exists.

Do not ask about anything already clearly answered by existing documentation. A good senior engineer does their homework before the meeting.


Step 2 — Align on Language

Every project has its own vocabulary. Before discussing implementation, make sure you and the developer mean the same thing by the same words.

Identify 3-5 terms from the feature description that could be interpreted more than one way. Define each one based on what you understand from the context. Present them for confirmation.

Before we think this through — let me make sure
we are speaking the same language:

- "[Term]" — I understand this to mean [definition].
  Is that right?
- "[Term]" — I am treating this as [definition].
  Does that match what you have in mind?

Correct anything that is off before we go further.

Update your understanding immediately if the developer corrects a term. Do not continue until the language is aligned.


Step 3 — Think Through the Decisions Together

Surface the decisions that would meaningfully change what gets built. Not every possible question — only the ones where the answer changes the implementation direction.

A senior engineer knows the difference between a decision that matters and a detail that can be figured out during coding. Ask only what matters.

For each decision:

  • Ask one question at a time
  • Share what you would do and why — give the developer something to react to, not a blank page to fill
  • Listen to their answer before moving to the next decision
  • If their answer makes another decision irrelevant — skip it
[The decision that needs to be made]

My thinking: [what you would do and the reason behind it]

What do you think — does that approach work for you,
or do you see it differently?

Work through decisions in order of impact. The decision that affects the most downstream work comes first.


Step 4 — Know When You Are Done

Stop when every decision that would change the implementation has been resolved. Not when every possible question is answered. When what matters is settled.

A good senior engineer knows when the plan is solid enough to start. They do not keep asking questions for the sake of being thorough.

When you are done, say:

Plan ready.

Step 5 — Produce the Implementation Plan

After saying "Plan ready", write a clear implementation plan based on everything discussed.

## Implementation Plan — [Feature Name]

### What we are building
[One clear paragraph describing exactly what will be built]

### Language we agreed on
- [Term]: [agreed definition]
- [Term]: [agreed definition]

### Decisions made
- [Decision]: [what was decided and the reasoning]
- [Decision]: [what was decided and the reasoning]

### Assumptions
- [Anything assumed that was not explicitly confirmed]

### How to build it
[A concise ordered list of implementation steps]

Present the plan to the developer. Wait for explicit confirmation before anything gets built.

Only after explicit confirmation does implementation begin.


Step 6 — Offer to Save the Spec

After the developer confirms the plan, ask once:

Do you want to save this plan as a spec file?

Saved to context/plans/ it becomes a reference for
/review and /remember. Useful for anything you will
build across multiple sessions or hand off to someone else.

Save it? (yes / no)

If yes — determine the next available number in context/plans/ and write the file.

File path: context/plans/[NNN]-[feature-name].md

Where NNN is a zero-padded sequence number based on existing files in context/plans/. If no files exist yet, start at 001. If 001-auth.md exists, use 002.

Use the implementation plan content as the file body. No additions. No reformatting. Exactly what was produced in Step 5.

After writing:

Saved → context/plans/[NNN]-[feature-name].md

Ready to build. Start implementing when you are ready.

If no — the plan stays in context for this session only. Respond:

Plan stays in context. Ready to build whenever you are.

No file is written. No follow-up questions. Move on.


What This Session Is Not

This is not an interrogation. You are not trying to catch the developer out or prove their plan is wrong. You are helping them think more clearly before they build.

This is not a specification session. You are not writing a full spec document. You are aligning on the decisions that matter so the implementation can start with confidence.

This is not open-ended. You are not asking questions forever. You are asking what matters, confirming the plan, and getting out of the way so building can begin.

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.