superpowers-sage:plan-generator

Name: superpowers-sage:plan-generator
Availability: InStock
Author: codigodoleo

Transform approved architecture specs into executable implementation plans with dependency graphs.

13|Updated Mar 19, 2026

Search Tags:#architecture #execution-plan #dependency-graph #plan-generation #anti-drift #plan-format #component-plans

Ready to run

npx skills add https://github.com/codigodoleo/superpowers-sage --skill superpowers-sage-plan-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superpowers-sage:plan-generator
Source: https://github.com/codigodoleo/superpowers-sage/tree/main/skills/plan-generator
Command: npx skills add https://github.com/codigodoleo/superpowers-sage --skill superpowers-sage-plan-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan Generator transforms approved architecture specifications into executable implementation plans, bridging the gap between design and delivery.

Core Features & Use Cases

Preflight validation to ensure specs align with claimed sources
Parse architecture into concrete implementation units and a dependency graph
Generate structured plan directories with per-component plans, design guides, and visual checks
Enforce plan consistency and drift prevention with anti-drift rules
Handoff execution-ready plans to the building and verifying skills for deployment

Quick Start

Provide an approved architecture spec path to Plan Generator to generate an execution plan.

Frequently Asked Questions about superpowers-sage:plan-generator

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

FAQPage Schema

How do I convert an approved architecture spec into an executable implementation plan?▼

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.

How does dependency graph generation work for component plans?▼

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.

What is plan drift prevention and when do I need it for software architecture execution?▼

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.

Can I use an architecture spec without preflight validation to generate execution plans?▼

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.

What's the best way to structure per-component plans for staged delivery?▼

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.

What are the limitations of generating implementation plans from architecture specs?▼

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.