spec-kit-skill

Automate constitution-based specification and feature development with the GitHub Spec-Kit workflow.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/billlzzz26/note-taker-convex-ai-convex --skill spec-kit-skill-billlzzz26
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-kit-skill
Source: https://github.com/billlzzz26/note-taker-convex-ai-convex/tree/main/.agents/skills/spec-kit-skill
Command: npx skills add https://github.com/billlzzz26/note-taker-convex-ai-convex --skill spec-kit-skill-billlzzz26

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Constitution-based feature development can be hard to start and govern consistently across teams. This Skill provides a structured, repeatable seven-phase workflow and artifact coordination using the GitHub Spec-Kit integration.

Core Features & Use Cases

  • 7-phase workflow covering Constitution, Specify, Clarify, Plan, Tasks, Analyze, and Implement.
  • CLI-driven guidance that organizes specifications, plans, and tasks and stores outputs under .specify/specs/NNN-feature-name/.
  • Discoverability and triggers that help teams apply the workflow in real projects.

Quick Start

Install the Spec-Kit CLI, initialize your project, and begin a feature with the 7-phase workflow.

Frequently Asked Questions about spec-kit-skill

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

FAQPage Schema
What is a constitution-driven spec workflow for feature development?

This Skill automates constitution-based specification using a 7-phase workflow: Constitution, Specify, Clarify, Plan, Tasks, Analyze, and Implement. Each phase gates the next, storing artifacts under .specify/specs/NNN-feature-name/ to ensure alignment and reproducible governance.

How do I start a feature using the GitHub Spec-Kit 7-phase process?

To start a feature, install the Spec-Kit CLI, initialize your project, and begin the 7-phase workflow. The process guides you through Constitution, Specify, Clarify, Plan, Tasks, Analyze, and Implement, organizing all outputs under .specify/specs/NNN-feature-name/.

Can I use phase-driven project management for existing software engineering projects?

Yes, phase-driven project management applies to existing projects by integrating the GitHub Spec-Kit workflow. It enforces phase-gated guidance and artifact alignment, bringing reproducible governance to ongoing feature development without disrupting current codebases.

Do I need to install dependencies before setting up the Spec-Kit CLI workflow?

Yes, you need to install the Spec-Kit CLI to initialize the project environment and begin the 7-phase feature workflow. The CLI drives the guidance, organizes specifications, and stores outputs under the .specify/specs/ directory structure.

How does phase-gated governance improve feature development over standard workflows?

Phase-gated governance improves feature development by enforcing sequential progression through seven distinct phases, from Constitution to Implement. This prevents skipping specification or clarification steps, ensuring artifact alignment and reproducible governance across the entire feature lifecycle.

What are the limitations of applying a 7-phase constitution workflow to small tasks?

The 7-phase constitution workflow introduces overhead that may not suit small or rapid tasks. It requires generating artifacts across Specify, Clarify, Plan, Tasks, Analyze, and Implement phases, which is designed for projects needing strict reproducible governance rather than lightweight updates.