plan

Convert design docs and SPEC.md into executable implementation plans.

1|Updated Apr 17, 2026

Search Tags:#planning #documentation #execution #spec #plan #task-management

Ready to run

npx skills add https://github.com/justincordova/agents --skill plan-justincordova

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/justincordova/agents/tree/main/skills/plan
Command: npx skills add https://github.com/justincordova/agents --skill plan-justincordova

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan creation transforms a design spec or brainstorm output into a clear, actionable implementation plan that guides code, docs, and tests.

Core Features & Use Cases

Convert design docs and SPEC.md into detailed tasks with milestones and ownership.
Propose file paths, code shapes, tests, and verification criteria to enable deterministic execution.
Serve as a handoff between brainstorming/spec phases and execution, ensuring alignment and traceability.

Quick Start

Provide your SPEC, brainstorm output, or design doc, and I will generate an executable plan outlining tasks, required files, and verification steps.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I turn a design spec into an executable implementation plan?▼

To turn a design spec into an executable implementation plan, provide your SPEC.md or brainstorm output. The tool translates requirements into detailed tasks, proposed file paths, and verification criteria for deterministic execution.

What is the best way to map SPEC.md requirements to specific code files and tests?▼

Mapping SPEC.md requirements to code and tests involves proposing specific file paths, code shapes, and verification steps. This ensures traceability and aligns task delineation with execution across documentation and testing.

Can I generate task milestones with ownership directly from brainstorm output?▼

Yes, you can generate task milestones with ownership directly from brainstorm output. The process converts design docs into detailed tasks, ensuring clear delineation and alignment before execution begins.

Do I need a completed SPEC.md before creating implementation tasks?▼

You need a completed SPEC.md, brainstorm output, or design doc to create implementation tasks. The planning process uses these inputs to outline required files, milestones, and verification steps for execution.

How does spec-driven planning handle verification criteria for code execution?▼

Spec-driven planning handles verification criteria by proposing specific tests and validation steps alongside code shapes. This ensures deterministic execution and confirms that the generated tasks satisfy the original spec requirements.