speckit

A specification-driven development workflow for Claude Code. Provides slash commands, agent definitions, hook scripts, and templates that enforce an 8-phase pipeline: constitution, specify, clarify, plan, checklist, tasks, analyze, implement. Optionally integrates with Beads (persistent issue tracker) and Linear.

This is a framework, not a standalone application. You copy its .claude/ and .specify/ directories into your project.

Status

Working framework used across multiple projects. Requires Claude Code CLI. No standalone runtime.

Pipeline

/speckit.constitution  ->  define project principles
/speckit.specify       ->  write feature spec (WHAT/WHY)
/speckit.clarify       ->  resolve ambiguities
/speckit.plan          ->  create technical plan (HOW)
/speckit.checklist     ->  generate quality checklist
/speckit.tasks         ->  produce dependency-ordered task list
/speckit.analyze       ->  cross-artifact validation
/speckit.implement     ->  execute implementation with test gates

Contents

Slash Commands (15)

Command	Phase
speckit.constitution	Define architectural principles
speckit.specify	Create feature specification
speckit.clarify	Resolve ambiguities in spec
speckit.plan	Write technical implementation plan
speckit.checklist	Generate quality validation checklist
speckit.tasks	Produce task list with dependencies
speckit.analyze	Cross-artifact consistency check
speckit.implement	Execute tasks with test gates
speckit.fix	Quick fix bypass (skips full workflow)
speckit.taskstoissues	Convert tasks to GitHub issues
speckit.linear.import	Import issue from Linear
speckit.linear.export	Export tasks to Linear sub-issues
speckit.linear.sync	Bidirectional Linear sync
speckit-workflow-v2	Full workflow orchestration
speckit-orchestrate	Quick workflow orchestration

Agents (7)

Agent	Role
openapi-spec-author	API design and contract validation
backend-api-engineer	Backend TDD implementation
frontend-react-engineer	Frontend React/TypeScript
integration-tester	E2E and integration testing
spec-validator	Spec quality validation
consistency-checker	Cross-artifact consistency
beads-sync	Beads issue synchronization

Skills (4)

Skill	Purpose
spec-kit-workflow	Workflow phase guidance
beads-integration	Persistent memory patterns
spec-validation	Spec quality validation
project-standards	Constitution principles

Scripts (10)

Located in .specify/scripts/bash/:

Script	Purpose
common.sh	Shared utilities
check-prerequisites.sh	Validate workflow state
create-new-feature.sh	Initialize feature branches
create-beads-epic.sh	Create Pivotal-style Beads epics
create-beads-issues.sh	Bulk import tasks with dependencies
install-hooks.sh	Set up git hooks
pre-push-ci.sh	Pre-push CI validation
setup-plan.sh	Initialize plan structure
update-agent-context.sh	Refresh agent context files
update-tasks-with-beads-ids.sh	Link tasks to Beads issues

Hooks (5)

Hook	Trigger
phase-gate.sh	Enforces phase ordering
post-edit.sh	Runs after file edits
pre-compact.sh	Runs before context compaction
session-start.sh	Runs at session start
test-gate.sh	Enforces 100% test pass after edits

Templates (7)

In .specify/templates/: spec, plan, tasks, checklist, agent-file, pre-commit-hook, and a GitHub Actions test-gate workflow.

Installation

git clone https://github.com/jmanhype/speckit.git
cd your-project
cp -r /path/to/speckit/.specify ./
cp -r /path/to/speckit/.claude ./
chmod +x .claude/hooks/*.sh

Or use the install script:

curl -fsSL https://raw.githubusercontent.com/jmanhype/speckit/main/install.sh | bash

Optional: Beads Integration

brew tap steveyegge/beads && brew install bd
bd init

Optional: Linear Integration

Configure in .mcp.json per the example in .mcp.json.linear-example. Requires a Linear API key.

Included Demo

neon-compliance-demo/ contains an Elixir/Phoenix application built using this framework. It includes a backend with rate limiting, health endpoints, and tests, plus contract definitions (OpenAPI, AsyncAPI).

Limitations

• Requires Claude Code CLI; does not work with other AI coding assistants
• install.sh references a placeholder repo URL that must be updated for forks
• No automated tests for the framework itself (the test-gate hook tests your project, not speckit)
• Linear integration requires manual MCP server configuration
• The act dependency (for local CI) must be installed separately
• The self-improve.yml GitHub Action references external tooling