02-plan

Generate an execution-ready project plan with TDD-gated implementation units.

29|2|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/leing2021/super-pi --skill 02-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 02-plan
Source: https://github.com/leing2021/super-pi/tree/main/skills/02-plan
Command: npx skills add https://github.com/leing2021/super-pi --skill 02-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It converts a brainstormed set of requirements into an execution-ready implementation plan, so you can move from ideas to safe, test-driven work with clear unit boundaries and checkpoints.

Core Features & Use Cases

  • Stage discipline with TDD gates: Enforces RED → GREEN → REFACTOR verification rules for every implementation unit to prevent unchecked coding.
  • Project-aware planning: Loads project workflow and testing rules, detects the project language, and applies language- and web-specific rule sets when needed.
  • Solution reuse via evidence-first search: Runs a grep-first solution search across project and global solution repositories, reads frontmatter for scoring, then fully reads the top candidates to inform the plan.
  • Incremental plan updates: When a plan already exists, uses plan diffing to patch incrementally rather than rewriting from scratch.
  • Optional CEO Review: Offers strategic review modes (CEO/Strict) that can revise the plan before handing off to execution.

Quick Start

Use this skill after you have a brainstorm artifact ready, then ask your agent to produce the plan and hand off to the next step for execution.

Frequently Asked Questions about 02-plan

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

FAQPage Schema
How do I turn brainstormed requirements into a TDD execution plan?▼

You can convert brainstormed requirements into an execution-ready plan using TDD-gated implementation units. This enforces RED→GREEN→REFACTOR verification rules for every unit to prevent unchecked coding and establish clear boundaries.

What's the best way to create implementation units with checkpointing for a new project?▼

The best way to create implementation units with checkpointing is to load project workflow and testing rules, detect the project language, and apply language-specific rule sets. This ensures the plan aligns with your project's specific configuration before execution.

Can I reuse existing code solutions when generating a project plan?▼

Yes, you can reuse existing code solutions when generating a project plan by running a grep-first solution search across project and global solution repositories. It reads frontmatter for scoring and fully reads top candidates to inform the plan.

How do I incrementally update an existing TDD plan without rewriting it?▼

You incrementally update an existing TDD plan by using plan diffing to patch the existing document rather than rewriting it from scratch. The plan artifact is written under docs/plans/ to maintain a clear record.

Does the planning workflow support strategic review before code execution?▼

Yes, the planning workflow supports strategic review before code execution by offering optional CEO Review modes. These modes can revise the plan before handing off to the 03-work execution step.