spec-kit

GitHub Spec-Kit integration for Specification-Driven Development - define WHAT and HOW before coding

View on GitHub
Author Dev GOM
Namespace @Dev-GOM/dev-gom-plugins
Category productivity
Version 2.3.2
Stars 57
Downloads 4
self.md verified
Table of content

GitHub Spec-Kit integration for Specification-Driven Development - define WHAT and HOW before coding

Installation

npx claude-plugins install @Dev-GOM/dev-gom-plugins/spec-kit

Contents

Folders: commands

Files: README.ko.md, README.md

Documentation

한국어 문서

Seamless integration of GitHub Spec-Kit with Claude Code for Specification-Driven Development (SDD).

Overview

This plugin brings GitHub’s Spec-Kit methodology into Claude Code, enabling a structured approach to software development:

ConstitutionSpecificationPlanTasksImplementation

Instead of jumping straight into coding, define WHAT you’re building (specification) and HOW you’ll build it (plan) before writing a single line of code.

💡 What is Spec-Kit? A GitHub-developed framework for Specification-Driven Development that helps teams define clear requirements and plans before implementation. Learn more at github.com/github/spec-kit

Features

Prerequisites

This plugin requires external tools:

  1. uv (Python package manager)

    • macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh
    • Windows: powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
  2. specify-cli (GitHub Spec-Kit CLI)

    • Install: uv tool install specify-cli --from git+https://github.com/github/spec-kit.git

The plugin will guide you through installation if not detected.

Commands

Core Workflow

CommandDescriptionWhen to Use
/spec-kit:initInitialize spec-kit projectStarting new project
/spec-kit:checkCheck installation statusTroubleshooting setup
/spec-kit:constitutionDefine project principlesBefore any feature work
/spec-kit:specifyWrite feature specificationsDefining WHAT to build
/spec-kit:planCreate technical planDefining HOW to build
/spec-kit:tasksBreak down into tasksPlanning implementation
/spec-kit:implementExecute tasksDuring development

Utility Commands

CommandDescriptionWhen to Use
/spec-kit:clarifyResolve ambiguitiesWhen specs unclear
/spec-kit:analyzeAnalyze project statusReview progress
/spec-kit:checklistRun quality gatesBefore commit/release

Workflow Example

# 1. Initialize project
/spec-kit:init

# 2. Establish project constitution (principles & standards)
/spec-kit:constitution

# 3. Write feature specification (WHAT to build)
/spec-kit:specify

# 4. Create technical plan (HOW to build)
/spec-kit:plan

# 5. Break down into tasks
/spec-kit:tasks

# 6. Implement step by step
/spec-kit:implement

# 7. Check quality gates
/spec-kit:checklist

Iterative Workflow

Spec-Kit is iterative by design. You can revise earlier stages as you learn more during implementation.

When to Update Earlier Stages

You should update specs, plans, or constitution when:

1. Re-run Commands (Best Practice) ✅

Simply re-run the command to update that stage. Claude will maintain context and help refine:

# Need to change specification?
/spec-kit:specify

# Need to revise technical plan?
/spec-kit:plan

# Need to update constitution?
/spec-kit:constitution

Why this is best:

2. Use Clarify for Specific Issues

When you need to resolve ambiguities or update specific sections:

# Clarify ambiguous parts
/spec-kit:clarify

# Then regenerate affected stages
/spec-kit:plan
/spec-kit:tasks

When to use:

3. Direct File Editing (Use Sparingly)

Only for minor cosmetic changes:

# Edit files directly in .specify/memory/
# - constitution.md
# - specification.md
# - plan.md

# Then regenerate downstream stages
/spec-kit:tasks

Only use for:

Avoid for:

Cascade Updates

After updating an earlier stage, regenerate downstream sta

…(truncated)

Source

View on GitHub

Tags: productivity specificationplanningworkflowsddgithubspec-kitconstitutiondocumentationproject-management