superpowers-sage:plan-generator

To generate an executable implementation plan, you provide an approved architecture spec path to the Skill. It parses the spec, validates alignment, and outputs a structured plan directory with per-component plans and acceptance criteria for staged delivery.

Dependency graph generation parses your architecture spec into concrete implementation units, mapping their relationships to assign an execution strategy. This ensures correct staging order and prevents drift during actual component plan creation.

Plan drift prevention enforces consistency between your approved architecture spec and the generated execution plan. You need it during staged delivery to ensure implementation units and per-component plans remain strictly aligned with the original design.

No, preflight validation ensures your architecture specs align with claimed sources before generating execution plans. Skipping it risks creating inconsistent component plans and invalid dependency graphs, compromising the entire structured plan directory output.

The best way to structure per-component plans is using a standardized plan directory with frontmatter templates. This approach enforces plan consistency, includes visual checks, and defines clear acceptance criteria for each implementation unit.

A limitation is that the Skill only accepts approved architecture specifications as input. It cannot generate execution plans from unstructured notes or incomplete designs, requiring fully validated specs to produce accurate dependency graphs and component plans.