plan

Decomposes approved specs into ordered TDD implementation tasks with verification commands and acceptance proofs.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill plan-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/greglas75/zuvo/tree/main/skills/plan
Command: npx skills add https://github.com/greglas75/zuvo --skill plan-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature spec or rough idea into an executable implementation plan is error-prone: tasks get mis-sized, dependencies get missed, and requirements silently drop out. This Skill produces a rigorous, task-by-task TDD plan where every task has exact verification commands, acceptance proofs, and explicit dependency ordering. ## Core Features & Use Cases - Multi-agent architecture analysis: Dispatches Architect, Tech Lead, and QA Engineer sub-agents sequentially to map component boundaries, select patterns and libraries, and assess testability before any task is written. - TDD task decomposition: Synthesizes agent reports into ordered tasks following RED-GREEN-Verify-Commit, with complexity ratings, failure strategies, and file-limit enforcement. - Independent plan review: A plan-reviewer agent validates spec coverage, dependency correctness, acceptance-proof executability, and fidelity to user-provided design artifacts. - Use Case: After approving a brainstorm spec for a new billing feature, run the plan skill to get a dated plan document in docs/specs/ with 5-10 milestone tasks, each carrying exact test commands and per-AC proof blocks ready for the execute phase. ## Quick Start Ask the AI to run the plan skill on your approved spec at docs/specs/my-feature-spec.md to generate a TDD implementation plan.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a feature spec into a TDD implementation plan?

Run the plan skill against an approved spec file in docs/specs/. It dispatches architecture, tech-lead, and QA analysis agents, then synthesizes their reports into ordered RED-GREEN-Verify-Commit tasks with exact test commands and acceptance proofs.

Can I create an implementation plan without a written spec?

Yes. The plan skill supports inline mode where your message is the planning input. It extracts the goal, scope, and constraints from your description, asks one clarifying question if too vague, and marks the plan as planning_mode: inline.

How does the plan skill validate task dependencies?

Every task must declare dependencies tracing concrete reads of prior tasks' files, symbols, or schema columns, and dependencies may only point to lower-numbered tasks. The plan-reviewer agent fails plans with circular, forward, missing, or unconsumed dependencies.

What happens when a plan has too many tasks?

Plans target 5-10 milestone tasks; more than 12 is treated as a planning smell. The skill enforces a scope-split rule that divides large migrations or cutovers into sequential plans shipped as separate PRs, typically compat, runtime cutover, then legacy removal.

Does the plan skill work with user-provided design artifacts?

Yes. When a prototype, HANDOFF.md, or mockup is supplied, it is treated as the source of truth. The skill extracts a Design Constraints checklist, ports working prototype code component-by-component, and hard-stops on any architecture decision contradicting a constraint.