speckit-story

Generate specs, plans, tasks, and verification reports from existing code.

15|5|Updated Feb 10, 2026

Search Tags:#automation #planning #specification #validation #story #agile #speckit

Ready to run

npx skills add https://github.com/connor-git-yaml/cc-plugin-market --skill speckit-story

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-story
Source: https://github.com/connor-git-yaml/cc-plugin-market/tree/main/plugins/spec-driver/skills/speckit-story
Command: npx skills add https://github.com/connor-git-yaml/cc-plugin-market --skill speckit-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-story enables fast requirement realization by skipping the research phase and delivering end-to-end work in five stages: specification, planning, tasks, implementation, and verification.

Core Features & Use Cases

No-research fast orchestration: Based on existing code and specs, directly generate incremental specs, a technical plan, task breakdown, and implementation strategy.
Five-stage workflow: Covers specification, planning, tasks, implementation, and verification with gating and parallel execution where possible.
Governance and risk controls: Gate policies (GATE_DESIGN, GATE_TASKS, GATE_VERIFY) and implement authorization checks to keep changes scoped.
Use cases: Ideal for small to medium changes that require rapid validation and delivery.

Quick Start

Trigger the skill with a natural language requirement using /spec-driver:speckit-story <your requirement> to start the fast-path workflow.

Frequently Asked Questions about speckit-story

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

FAQPage Schema

How do I automate specification and planning for rapid agile story delivery?▼

Automating specification and planning for agile delivery is achieved by skipping research and generating incremental specs, technical plans, tasks, and implementation directly from existing code. This fast-path workflow executes five stages: specification, planning, tasks, implementation, and verification.

Can I generate task breakdowns and technical plans from existing code without a research phase?▼

Yes, you can generate task breakdowns and technical plans from existing code without research by using a no-research fast orchestration process. It analyzes existing code and specifications to directly drive outputs like spec.md, plan.md, and tasks.md for incremental changes.

How does gate validation work in an automated specification and implementation workflow?▼

Gate validation enforces scoped changes through GATE_DESIGN, GATE_TASKS, and GATE_VERIFY checkpoints during the five-stage workflow. These gate policies implement authorization checks and risk controls, ensuring specification, planning, and implementation stages meet governance requirements before proceeding.

What is the best way to validate small to medium code changes quickly end-to-end?▼

The best way to validate small to medium code changes quickly is using a five-stage workflow that skips research and delivers end-to-end work. It covers specification, planning, tasks, implementation, and verification, producing verification reports to confirm rapid validation.

Does fast-path agile story generation require prior specifications and existing code context?▼

Fast-path agile story generation requires existing code and prior specifications as input context to function correctly. Because it skips the research phase, it relies entirely on analyzing your current codebase and existing specifications to generate incremental specs, technical plans, and task breakdowns.

When should I avoid using a no-research fast orchestration workflow for requirement realization?▼

You should avoid no-research fast orchestration for large projects lacking existing code or specifications, as it skips the research phase entirely. It is designed specifically for small to medium changes requiring rapid validation, relying on current code context to drive generation safely.