spec-to-plan

Generate implementation plans from specification documents in docs/specs.

1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/jarrett-au/cc-config-starter --skill spec-to-plan-jarrett-au
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-to-plan
Source: https://github.com/jarrett-au/cc-config-starter/tree/main/skills/spec-to-plan
Command: npx skills add https://github.com/jarrett-au/cc-config-starter --skill spec-to-plan-jarrett-au

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes the software development project planning process, ensuring that every development task begins with a well-defined specification document and a detailed implementation plan.

Core Features & Use Cases

  • Spec Document Creation: Guides users to create comprehensive specification documents for new features, refactoring tasks, or complex development efforts.
  • Automated Plan Generation: Leverages existing spec documents to automatically generate detailed task breakdowns, progress tracking templates, and issue logs.
  • Use Case: When a user requests a new feature, this Skill ensures they first complete a detailed spec in docs/specs/, then automatically generates a task_plan.md, progress.md, and findings.md in a corresponding docs/plans/ directory.

Quick Start

Use the spec-to-plan skill to generate a project plan based on the specification document located at docs/specs/20231027_user_profile_update_spec.md.

Frequently Asked Questions about spec-to-plan

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

FAQPage Schema
How do I generate an implementation plan from a specification document?▼

To generate an implementation plan from a specification document, the system reads your spec file and outputs a structured task plan, progress tracker, and findings log to maintain consistency and traceability.

What's the best way to standardize project planning for new feature development?▼

Standardizing project planning for new feature development requires guiding users to create comprehensive specification documents first, then automatically generating actionable implementation plans to ensure a structured approach from initial requirements to execution.

Do I need specific file naming conventions for software development specifications?▼

Yes, specific file naming conventions for software development specifications are required. Adhering to structured naming in docs/specs and docs/plans directories maintains project consistency and traceability.

Can I use this workflow automation for code refactoring tasks?▼

Yes, you can use this workflow automation for code refactoring tasks. It supports workflows for new feature development, code refactoring, and complex task management by ensuring a structured approach from initial requirements to execution.

What files are automatically generated when creating a task plan from a spec?▼

When creating a task plan from a spec, the files automatically generated include a task_plan.md for task breakdowns, a progress.md for tracking templates, and a findings.md for issue logs within the corresponding docs/plans directory.