agentleFS
tunahanaliozturktunahanaliozturk/atelier/skills/reviewing-plans/SKILL.md

reviewing-plans

Skill1 starsChanged 5 months agoMITView on GitHub

Use when the lead receives a draft plan, to review the plan itself before any work starts.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Reviewing Plans

Review a draft plan against four checks before presenting it to the user:

  1. Completeness: does every part of the goal map to a step? List gaps.
  2. Ordering and dependencies: is anything sequenced wrong or missing a dependency?
  3. Risk: which steps are risky or unknown, and is there a step to de-risk them?
  4. Capability coverage: for each step, is there a registered agent whose layer and task_kinds can do it? If a step has no owner, flag it and propose adding an agent. This is a pre-flight check; the lead does the actual per-task assignment later with the capability-routing skill.

Revise the plan to fix what you find, then hand it to the user gate.

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.