agentleFS
Sign inStart free
SemanticMatterSemanticMatter/autonomous-development/skills/implement-plan/SKILL.md

implement-plan

Skill3 starsChanged 49 days agoMITView on GitHub

Implement the currently accepted autonomous-development plan with tests and documentation while preserving unrelated changes and safety boundaries.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use iterate-plan, validate-plan 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.
  • corticalstackSkill

    iterate-plan

    Revise an existing implementation plan in flow/plans/ based on feedback, researching when needed. Explicit-only; run only when invoked via /iterate-plan or explicitly asked.

    Also in 5 projects that use this

  • shawn-dumasSkill

    validate-plan

    Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.

    Also in 4 projects that use this

  • parcadeiSkill

    describe-pr

    Generate comprehensive PR descriptions following repository templates

    Also in 4 projects that use this

  • joshuaalpuertoSkill

    research-codebase

    Conducts structured research across a codebase to answer questions about architecture, components, and data flow. Use when investigating how code works, where functionality lives, or how systems interact. Decomposes questions, runs parallel investigations, synthesizes findings with file:line references, and produces persistent research documents.

    Also in 4 projects that use this

  • JetBrainsSkill

    create-plan

    Research the codebase and create an implementation plan with architecture notes, design document, and track decomposition. Use when starting a new feature or large change.

    Also in 8 projects that use this

  • JetBrainsSkill

    review-plan

    Manually re-run the autonomous plan review (Phase 2 — consistency + structural). The same review runs automatically as the first phase of /execute-tracks; this command is for re-runs after inline replanning or whenever the plan needs explicit re-validation. TRIGGER when: user asks to re-validate the plan after inline replanning; user requests explicit plan review outside /execute-tracks. SKIP: /execute-tracks already running State 0 in this session (autonomous Phase 2 path will fire) — do not double-run.

    Also in 5 projects that use this

  • +1 more from JetBrains

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Read the current run's accepted artifacts.

    line 12
  2. Distinctive:

    Add tests for every changed behavior and regression.

    line 22
  3. Distinctive:

    Keep interfaces backward compatible unless the accepted specification explicitly requires a break.

    line 23
  4. Distinctive:

    Update affected documentation and examples.

    line 25
  5. Distinctive:

    Never push, merge, deploy, access production, rotate credentials, or apply irreversible migrations.

    line 28

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

Implement the accepted plan

Read the current run's accepted artifacts. Use controller.py show-run (or controller.py status --json) to find the paths under artifacts.accepted_spec and artifacts.accepted_plan, then read those files along with repository instructions and relevant source/tests.

Then:

  1. Confirm the workflow is active with controller.py status.
  2. Implement only accepted scope, incrementally.
  3. Preserve unrelated local modifications.
  4. Add tests for every changed behavior and regression.
  5. Keep interfaces backward compatible unless the accepted specification explicitly requires a break.
  6. Include safe migration and rollback paths where applicable.
  7. Update affected documentation and examples.
  8. Set the phase to implemented when implementation is complete.

Never push, merge, deploy, access production, rotate credentials, or apply irreversible migrations.

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.

Check your setup, free