agentleFS
loganware05loganware05/captains-compass-cursor/.cursor/skills/implementation-planning/SKILL.md

implementation-planning

Skill2 starsChanged 31 days agoMITView on GitHub

Creates an approval-gated implementation plan before product changes

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use systematic-debugging.

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.
  • OpenAISkill

    systematic-debugging

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 6

    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:

    Use this Skill for any feature, bug fix, refactor, database change, infrastructure change, or other task that modifies product behavior.

    line 10
  2. Distinctive:

    Read the required project documents.

    line 24
  3. Distinctive:

    Do not modify product implementation files.

    line 45
  4. Distinctive:

    Do not create migrations.

    line 46
  5. Distinctive:

    Do not begin a feature branch.

    line 47
  6. Distinctive:

    Do not claim that approval is implied.

    line 48

“Common” is measured: kept by at least 6 in 10 of the 13 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

Implementation Planning

Use this Skill when

Use this Skill for any feature, bug fix, refactor, database change, infrastructure change, or other task that modifies product behavior.

Inputs

  • User request
  • Repository structure
  • Existing project documentation
  • Current Git state
  • Relevant issue
  • Technical constraints

Procedure

  1. Read the required project documents.
  2. Inspect relevant implementation files.
  3. Load Skill capability-planning and run ./scripts/capability-plan.sh for the objective; merge rendered sections into IMPLEMENTATION_PLAN.md.
  4. Identify current behavior.
  5. Define desired behavior.
  6. Identify assumptions and open questions.
  7. Identify affected systems.
  8. Define independent workstreams (align with task graph when present).
  9. Define tests and evidence.
  10. Define migration and rollback requirements.
  11. Define time, cost, and iteration limits.
  12. Write IMPLEMENTATION_PLAN.md.
  13. Set its status to AWAITING APPROVAL.
  14. Present the plan and stop.

Output

A complete IMPLEMENTATION_PLAN.md ready for human approval.

Prohibited actions

  • Do not modify product implementation files.
  • Do not create migrations.
  • Do not begin a feature branch.
  • Do not claim that approval is implied.

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.