spec-kit-skill

Coordinates constitution-based feature development with GitHub Spec-Kit across seven workflow phases.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tense-i/stock-market-simulator --skill spec-kit-skill-tense-i
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-kit-skill
Source: https://github.com/tense-i/stock-market-simulator/tree/main/skills/spec-kit-skill
Command: npx skills add https://github.com/tense-i/stock-market-simulator --skill spec-kit-skill-tense-i

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Constitution-driven workflows and governance for feature development using GitHub Spec-Kit, enabling consistent spec-driven delivery.

Core Features & Use Cases

  • Integrates with the GitHub Spec-Kit CLI to guide all seven phases (Constitution, Specify, Clarify, Plan, Tasks, Analyze, Implement) of feature development.
  • Provides artifact management conventions, frontmatter-driven discovery, and repo-structure guidance for reproducible specs and automation.
  • Supports a governance-centric workflow that improves collaboration, traceability, and quality across teams.

Quick Start

Initialize a constitution-driven spec workflow in your project using the Spec-Kit CLI.

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 specification workflow for feature development?

A constitution-driven specification workflow establishes foundational governance rules before feature development begins. Using GitHub Spec-Kit, it coordinates a seven-phase process from Constitution to Implement, ensuring consistent spec-driven delivery, traceability, and collaboration across teams.

How do I set up GitHub Spec-Kit CLI for constitution-based feature specs?

To set up the Spec-Kit CLI for constitution-based specs, initialize the workflow in your repository to define artifact management conventions. This establishes frontmatter-driven discovery and repo-structure guidance, enabling reproducible specifications and safe integration of scripts and references.

What are the seven phases of the Spec-Kit feature development workflow?

The seven phases of the Spec-Kit workflow are Constitution, Specify, Clarify, Plan, Tasks, Analyze, and Implement. This structured sequence guides teams through governance setup, specification drafting, clarification, planning, task breakdown, analysis, and final implementation.

Does the Spec-Kit workflow support frontmatter parsing for artifact discovery?

Yes, the Spec-Kit workflow supports frontmatter parsing to enable artifact discovery. It defines a specific metadata schema that allows safe integration and automated discovery of scripts, references, and assets within your repository structure.

Can I manage optional resources like scripts and assets within a Spec-Kit workflow?

Yes, you can manage optional resources like scripts and assets within a Spec-Kit workflow. The skill provides artifact management conventions and handles optional resources to ensure safe integration and reproducible specifications across your development teams.

When should I use a constitution-driven spec workflow instead of standard feature development?

Use a constitution-driven spec workflow when your teams need improved governance, collaboration, traceability, and quality. It is ideal for projects requiring reproducible specs and automation, providing a structured seven-phase process over standard ad-hoc development.