plan-spec

Generate detailed implementation specifications for project phases from an existing plan.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/ccam80/claude-orchestrator --skill plan-spec-ccam80
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-spec
Source: https://github.com/ccam80/claude-orchestrator/tree/main/skills/plan-spec
Command: npx skills add https://github.com/ccam80/claude-orchestrator --skill plan-spec-ccam80

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of translating high-level project plans into detailed, actionable specifications for software development.

Core Features & Use Cases

  • Detailed Spec Generation: Creates comprehensive specifications for individual phases of a project plan.
  • Collaborative Design: Facilitates user-driven design decisions by presenting options and tradeoffs clearly.
  • Use Case: After generating an overall implementation plan, use this skill to drill down into a specific phase, defining the exact files to create, modify, and test, ensuring all design choices are approved by the user.

Quick Start

Use the plan-spec skill to generate a detailed specification for the 'authentication' phase of the project.

Frequently Asked Questions about plan-spec

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

FAQPage Schema
How do I generate detailed implementation specifications from a high-level project plan?

Generate detailed implementation specifications by reading an existing implementation plan and collaborating on design decisions. This process defines exact files to create, modify, and test, translating high-level plans into actionable development phases.

What is the best way to ensure architectural consistency when creating phase specifications?

Ensure architectural consistency by reading project conventions and relevant source files before generating phase specifications. This approach checks existing structures and flags potential design issues against established project standards.

How do I define acceptance criteria and tests for a specific software development phase?

Define acceptance criteria and tests by drilling down into a specific phase of an existing implementation plan. The specification process outlines exact files to modify and test, ensuring all design choices meet project requirements.

Can I collaborate on design decisions and tradeoffs when writing software specifications?

Collaborate on design decisions by presenting options and tradeoffs clearly during specification generation. This user-driven approach ensures all architectural choices for files and tests are explicitly approved before development begins.

What files do I need before generating implementation specs for a software project?

Generating implementation specs requires reading an existing implementation plan file, project conventions, and relevant source files. These inputs provide the necessary architectural context to output consistent phase specifications.

How does collaborative design work when translating an implementation plan into code specifications?

Collaborative design works by interacting with the user to present design options and tradeoffs. This translates the overall implementation plan into a detailed specification for a chosen phase, requiring approval for all file modifications.