Русская версия: README.ru.md

speckeep — a lightweight Spec-Driven Development kit for dev agents and humans. It keeps specs, plans, tasks, and traceability in simple files so agents and people stay aligned without heavy process.

SpecKeep is the successor to DraftSpec (archived). Migrate with speckeep migrate.

# 1. Try it instantly — no project setup needed
speckeep demo ./my-demo

# 2. See what was created
speckeep dashboard ./my-demo

# 3. Init a real project
speckeep init my-project --lang en --shell sh --agents claude

That's it. You now have a project with constitution, spec, plan, tasks, inspect report, and data model — plus agent prompt files and AGENTS.md.

Teams using AI coding agents face a common problem: agents lose context between sessions, drift from requirements, and produce untestable code.

speckeep solves this with discipline per token — minimal file-based structure that keeps agents and humans on the same page:

• Specs with stable IDs (AC-*, RQ-*) — agents know exactly what to build and verify
• Tasks with surface maps and phase grouping — agents execute in order, one phase at a time
• Traceability (@sk-task annotations) — verify that every requirement is implemented and tested
• 10 agent adapters — Claude Code, Cursor, Copilot, OpenCode, aider, Windsurf, and more

Results in practice: agents produce correct code on first try more often, handoffs between sessions cost less context, and requirements stay reviewable by humans.

constitution → spec → [inspect] → plan → tasks → implement → verify → archive

Each phase loads only the minimum context. Optional workflow commands available at any phase: /speckeep.challenge, /speckeep.handoff, /speckeep.hotfix, /speckeep.scope, /speckeep.recap.

speckeep init [path]
speckeep refresh [path]
speckeep doctor [path] [--json]
speckeep dashboard [path]
speckeep check <slug> [path] [--json]
speckeep check [path] --all [--json]
speckeep feature <slug> [path]
speckeep features [path]
speckeep list-specs [path]
speckeep show-spec <name> [path]
speckeep trace <slug> [path]
speckeep export <slug> [path] [--output <file>]
speckeep demo [path]
speckeep archive <slug> [path]
speckeep list-archive [path] [--status <status>] [--since <YYYY-MM-DD>] [--json]
speckeep migrate [path]
speckeep add-agent | list-agents | remove-agent | cleanup-agents [path]
speckeep add-skill | list-skills | remove-skill | install-skills | skills-restore [path]

Linux / macOS:

VERSION=v0.5.1
curl -fsSL "https://raw.githubusercontent.com/bzdvdn/speckeep/${VERSION}/scripts/install.sh" | bash -s -- --version "${VERSION}"

Windows (PowerShell):

$version="v0.5.1"
$env:SPECKEEP_VERSION=$version
powershell -ExecutionPolicy Bypass -c "iwr -useb https://raw.githubusercontent.com/bzdvdn/speckeep/$version/scripts/install.ps1 | iex"

Add --add-to-path (Linux) or -AddToPath (Windows) to add the install directory to PATH.

Go users:

go install speckeep@latest

Build from source:

go build -ldflags "-X speckeep/src/internal/cli.Version=v0.5.1" -o bin/speckeep ./src/cmd/speckeep

speckeep init . --lang en --shell sh --agents claude

## Goal
Allow users to download the reports table as a CSV file.

## Acceptance Criteria

**AC-001** Export produces a file
Given the Reports page has at least one row
When the user clicks "Export CSV"
Then a .csv file downloads with column headers and all visible rows

**AC-002** Empty state is handled
Given the reports table is empty
When the user clicks "Export CSV"
Then a .csv with headers only downloads — no error shown

/speckeep.implement csv-export-for-reports
/speckeep.verify    csv-export-for-reports   # verdict: pass
speckeep archive    csv-export-for-reports .

speckeep check csv-export-for-reports
# Phase:  tasks → implement
# Tasks:  0 / 3 done
# Next:   /speckeep.implement csv-export-for-reports

Each feature lives under specs/<slug>/ with:

• spec.md — requirements (RQ-*) and acceptance criteria (AC-* with Given/When/Then)
• inspect.md (optional) — quality gate before planning
• plan.md — design decisions (DEC-*) and incremental delivery
• tasks.md — executable tasks with surface map and phase grouping
• data-model.md — entities, fields, invariants
• contracts/api.md, contracts/events.md (optional)
• verify.md — verification evidence

Annotate code during implementation:

// @sk-task T1.1 (AC-001)

Then verify with:

speckeep trace <slug> .

Supported out of the box: claude, codex, copilot, cursor, kilocode, opencode, trae, windsurf, roocode, aider.

Reusable guidance packages from local paths or git repos:

speckeep add-skill my-project --id architecture --from-local skills/architecture
speckeep install-skills my-project

Extended docs in docs/:

• Overview
• CLI Reference
• Workflow Model
• Architecture
• Agents
• Examples
• FAQ
• Glossary
• Roadmap

Project:

• Contributing
• Code of Conduct
• Security Policy
• MVP Definition
• Changelog

A reproducible terminal demo is available under demo/:

go build -o bin/speckeep ./src/cmd/speckeep
vhs demo/quick.tape

Requires Go 1.26+.

go test ./...
go vet ./...
go build -o bin/speckeep ./src/cmd/speckeep

Released under the MIT License.