refine-plan

Reviews and revises implementation plans for completeness and correctness against ticket requirements.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill refine-plan-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refine-plan
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/refine-plan
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill refine-plan-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementation plans often contain decision gaps and factual errors that surface only during coding, causing rework and drift from the original ticket. This Skill runs a structured review-and-revise round on a saved plan so it is validated against the codebase and requirements before orchestrated development begins. ## Core Features & Use Cases - Automated plan review: Delegates completeness and correctness analysis to a plan-reviewer subagent that checks the plan against the ticket and codebase. - Interactive decision resolution: Presents decision-gap findings as structured questions with recommended options, then feeds your answers to a plan-reviser subagent. - Provenance tracking: Stamps the revised plan with YAML frontmatter recording the authoring skill, refinement iteration, branch, commit, and timestamp. - Use Case: After saving a draft implementation plan for GitHub issue #537, run this Skill with the plan path and issue URL to catch missing decisions, answer reviewer questions, and receive a refined v2 plan ready for orchestration. ## Quick Start Refine the plan at artifacts/projects/myapp/tickets/537/20260310-080000Z_add-auth_plan.md against ticket https://github.com/org/repo/issues/537.

Frequently Asked Questions about refine-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an implementation plan before coding starts?

Invoke refine-plan with the saved plan file path and the ticket source (file path, GitHub issue URL, or other URL). It dispatches a plan-reviewer subagent that checks completeness and correctness, then a plan-reviser produces a refined v2 plan.

What inputs does plan refinement require?

Two arguments are required: the path to a saved plan artifact (such as the timestamped plan file from save-plan) and a ticket source, which can be a local file path, a GitHub issue URL fetched via gh, or another URL.

Does refine-plan modify the original plan file?

No, the original plan is never modified. All output goes to new artifact files: a review report and a separately timestamped revised plan stamped with provenance frontmatter including iteration count.

What happens when the plan review finds no issues?

If the reviewer reports zero findings, the reviser step is skipped entirely. The Skill reports that the plan is ready for implementation and presents next-step options such as orchestration or direct implementation.

Can refine-plan run multiple review rounds in one invocation?

No, it performs exactly one review-and-revise round per invocation by design. If the revision introduced significant scope changes, you can invoke it again on the revised plan as a separate run.