spec-driven-workflow

Analyze a codebase to generate a SPEC-first plan and decisions log.

19|3|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/changoo89/claude-pilot --skill spec-driven-workflow-changoo89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-workflow
Source: https://github.com/changoo89/claude-pilot/tree/main/.claude/skills/spec-driven-workflow
Command: npx skills add https://github.com/changoo89/claude-pilot --skill spec-driven-workflow-changoo89

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

## What problem does it solve? SPEC-first planning workflow helps teams analyze a codebase, extract requirements, and generate a concrete execution plan without touching the code.

## Core Features & Use Cases

  • Read-only codebase exploration: identify files, patterns, dependencies, and tests without modifying the repository.
  • Requirements capture and plan generation: convert user intent into a SPEC-first plan that guides downstream work.
  • Draft planning output: store plan drafts in .pilot/plan/draft for review and iteration.
  • Optional GPT delegation: consult gpt-delegation for architecture directions and risk assessment when needed.

### Quick Start Invoke /00_plan with a task description to begin the read-only SPEC-first planning flow and generate a draft plan in .pilot/plan/draft.

Frequently Asked Questions about spec-driven-workflow

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

FAQPage Schema
What is spec-first planning for software projects?

Spec-first planning analyzes a codebase in read-only mode to derive concrete requirements and a structured execution plan before any code is written. It extracts project intent into a draft plan and traceable decisions log for review.

How do I generate an execution plan from an existing codebase?

To generate an execution plan, invoke the planning workflow with a task description. It coordinates with planning-team agents to analyze files and dependencies, outputting a draft plan stored under .pilot/plan/draft for iteration.

Can I capture project requirements without modifying the repository?

Yes, you can capture requirements without modifying the repository. The workflow operates in a strictly read-only mode during codebase exploration, identifying patterns and tests while storing outputs separately in .pilot/plan/draft.

Does spec-first planning support GPT delegation for architecture decisions?

Yes, spec-first planning supports GPT delegation for architecture decisions. It optionally consults gpt-delegation to provide architecture directions and assess risks while generating your structured execution plan.

What are the limitations of read-only codebase exploration for planning?

The limitation of read-only codebase exploration is that it cannot directly modify code or apply fixes. It is restricted to deriving requirements and generating a draft plan, meaning downstream implementation requires separate execution tools.