speckit-feature

Coordinate ten-phase Spec-Driven Development workflows with Claude Code Task tools.

15|5|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/connor-git-yaml/cc-plugin-market --skill speckit-feature
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-feature
Source: https://github.com/connor-git-yaml/cc-plugin-market/tree/main/plugins/spec-driver/skills/speckit-feature
Command: npx skills add https://github.com/connor-git-yaml/cc-plugin-market --skill speckit-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Speckit-feature automates the end-to-end Spec-Driven Development workflow across ten phases, coordinating governance, parallel research, and artifact generation to reduce cycle time and miscommunication.

Core Features & Use Cases

  • Orchestrates a ten-phase Spec-Driven workflow including product research, technical research, synthesis, planning, implementation, and verification
  • Enables parallel execution of sub-tasks (research groups) with gating policies to manage risk
  • Generates and aggregates artifacts (product/tech research, synthesis, plan, tasks, verification) for traceability and auditability
  • Includes robust retry, fallback, and selective re-run mechanisms to improve reliability

Quick Start

Describe your feature request and let Speckit orchestrate the full 10-phase Spec-Driven workflow.

Frequently Asked Questions about speckit-feature

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

FAQPage Schema
How do I automate spec-driven development workflows with Claude Code?▼

Spec-driven development workflows are automated by orchestrating ten end-to-end phases using Claude Code Task tools, coordinating product discovery, research, synthesis, planning, implementation, and verification.

What is the best way to manage parallel research tasks in a spec-driven workflow?▼

Parallel research tasks are managed through orchestration phases that execute research groups concurrently while applying gating policies to control risk and aggregate phase artifacts for traceability.

Can I selectively re-run specific phases if my spec-driven workflow fails?▼

Yes, you can selectively re-run specific phases because the workflow includes robust retry, fallback, and selective re-run mechanisms to improve orchestration reliability and recover from failures.

How do gating policies work during feature discovery and implementation?▼

Gating policies manage risk during feature discovery and implementation by enforcing rules across orchestration phases, ensuring parallel sub-tasks meet criteria before proceeding to subsequent workflow steps.

Do I need Claude Code Task tools to coordinate spec-driven development?▼

Yes, Claude Code Task tools are required to coordinate the end-to-end spec-driven development workflow, as they drive the parallel task execution, phase gating, and artifact generation across ten phases.

How does artifact generation work across spec-driven orchestration phases?▼

Artifact generation works by creating and aggregating phase outputs including product research, tech research, synthesis, plans, tasks, and verification results to ensure full traceability and auditability.