agentleFS
ahmadrosidahmadrosid/nakama/.agents/skills/plan-review/SKILL.md

plan-review

Skill826 starsChanged 12 days agoMITView on GitHub

Review an implementation plan for major gaps, then revise the plan until no major issue remains. Use when asked to stress-test or improve a plan.

47 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan-execute, pr-comment 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.
  • longranger2Skill

    plan-execute

    Use when the user says "/plan-execute", "plan execute", "implement plan", or "execute plan" and provides a finalized plan file path to carry out. Claude orchestrates, Codex writes code, Claude reviews, and Codex fixes issues until the quality bar is met.

    Also in 4 projects that use this

  • BenjaminGSkill

    pr-comment

    This skill should be used when reviewing someone else's pull request and you want drafted review comments posted to GitHub — either gate / gate-wf findings (tier-marked) or pr-challenge's reviewer questions (unmarked) — each drafted through humanizer and posted as a standalone inline comment at its file:line, after one confirmation. Triggers on "post these as review comments", "comment the gate findings on the PR", "draft and post my review", "leave review comments", after a gate / gate-wf run or a pr-challenge pass on a PR you're reviewing.

    Also in 3 projects that use this

  • MicrosoftSkill

    spec-review

    Independent, multi-model review of a design or spec **before** any code is written, for the microsoft/winappcli repo. Activate when a contributor asks to "review this spec", "review my design", "review this design doc", "validate this approach", "should we build this", "spec review", "design review", or "feature review". Fans out parallel sub-agents — each doing its OWN research against the real codebase and ecosystem rather than trusting the spec — covering necessity & scope, approach & alternatives, feasibility vs reality, risks & unknowns, DX & user impact, and a different-model-family cross-check. Emits a decision-oriented recommendation (proceed / proceed-with-changes / reconsider) to stdout. This is the PRE-CODE companion to the pr-review skill (which reviews code already written); use spec-review at the design/spec stage, not on an implemented diff. Does NOT write code or edit the spec.

    Also in 3 projects that use this

  • AnthropicSkill

    office-hours

    Set up and run Claude Code office hours, including the calendar event when the champion's own calendar connector allows it. Use when a champion wants a regular time for teammates to bring problems.

    Also in 3 projects that use this

  • Hugging FaceSkill

    simplify

    Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.

    Also in 3 projects that use this

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 7

    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:

    Check claims about current code against the repository.

    line 13
  2. Distinctive:

    Look for major gaps in scope, feasibility, data flow, security, compatibility, failure handling, acceptance checks, tests, and required …

    line 14
  3. Distinctive:

    Check the final file for consistency and whitespace.

    line 17
  4. Distinctive:

    Keep the user's goal and scope.

    line 21
  5. Distinctive:

    Check whether proposed contracts fit real callers, schemas, transports, and data paths.

    line 23
  6. Distinctive:

    Treat missing labels, assignments, approvals, or other project gates as planning constraints.

    line 25
  7. Distinctive:

    Ask the user only when a material choice cannot be resolved from the plan, issue, project rules, or code.

    line 26

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

Review and revise an implementation plan

Review the plan against its issue, project rules, and current code. Fix major gaps in the plan itself. Continue until another evidence-based review finds no major issue.

Workflow

  1. Find the plan and read it. Read the referenced issue or specification and applicable project instructions.
  2. Check claims about current code against the repository. Use the codebase graph tools first when available. Read source only to verify relevant details.
  3. Look for major gaps in scope, feasibility, data flow, security, compatibility, failure handling, acceptance checks, tests, and required gates. Treat a gap as major when it can block delivery, break existing behavior, expose or lose data, or make success hard to verify.
  4. Revise the plan to fix verified gaps. Use the existing design and code where possible. State any unresolved decision or assumption clearly.
  5. Review the revised plan again against the same sources. Repeat until no major issue remains, or until a decision needs user input.
  6. Check the final file for consistency and whitespace. Do not implement the plan or change external systems unless the user asks.

Rules

  • Keep the user's goal and scope. Do not turn a review into a redesign or add optional features.
  • Separate verified facts from proposed design choices. Do not present a proposal as current project behavior.
  • Check whether proposed contracts fit real callers, schemas, transports, and data paths.
  • Include concrete acceptance checks and focused tests for risky or changed behavior.
  • Treat missing labels, assignments, approvals, or other project gates as planning constraints. Do not use them to stop plan review.
  • Ask the user only when a material choice cannot be resolved from the plan, issue, project rules, or code. Continue other review work first.
  • Finish with the plan path, the major gaps fixed, and any remaining unverified decisions or checks.

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.