create-a-plan

To turn a rough feature spec into an implementation plan, this Skill conducts a structured technical interview to define goals, constraints, serial prerequisites, and independent workstreams. It outputs the detailed technical plan to PLAN.md in the repository root.

Dependency analysis for software project planning identifies serial prerequisites and independent workstreams to enable parallel execution. This process extracts merge points and concrete tasks from your spec, ensuring multiple engineering teams can execute concurrently while preserving integration checkpoints.

Creating a technical plan with risk assessment and verification steps involves iterative discovery rounds that surface edge cases and assumptions. The resulting PLAN.md documents testing procedures, rollout and rollback guidance, and open questions alongside the implementation tasks.

Yes, you can use an existing RFC document to generate an actionable technical plan. By providing the path to your spec file, the Skill analyzes the existing information without repeating it, asking only focused discovery questions to map dependencies and parallel workstreams.

The best way to plan infrastructure projects for parallel teams is to map serial prerequisites and independent workstreams through focused discovery. This approach defines clear merge points and integration checkpoints, allowing teams to work concurrently without blocking each other.

When generating a technical plan from a brief idea, the main limitation is the need for iterative discovery rounds. The Skill must ask focused questions to surface unstated goals, constraints, and edge cases before it can accurately define dependencies and write PLAN.md.