# Documentation

## Specification

The SpecScore format — how to write specs that lint clean.

- [Overview](/specifications) — index of all specifications
- [Feature](/feature-specification) — the atomic unit of product specification
- [Plan](/plan-specification) — planning documents that bridge specs to execution
- [Task](/task-specification) — discrete units of work within a Plan
- [Acceptance Criteria](/acceptance-criteria-specification) — verification conditions for requirements
- [Repo Config](/repo-config) — `specscore.yaml` configuration reference
- [Source References](/source-references-specification) — code-to-spec traceability
- [Decision](/decision-specification) — Architecture Decision Records (ADRs)
- [Decisions Index](/decisions-index-specification) — canonical index of Decision documents
- [Lessons](/lesson-specification) — durable process-improvement rules with append-only occurrence evidence
- [Writing and migrating Lessons](/lessons) — practical guide to compact rules, safe occurrence context, and lossless legacy migration
- [Entities & Properties](/entities-and-properties) — the full entity model

## Writing good specs

Craft guidance for turning requirements into clean specs.

- [Asking Good Questions for Good Specs](/asking-good-questions) — how to question a fuzzy request into complete, unambiguous, verifiable acceptance criteria
- [Explained by example: a login feature](/example-login) — one feature through the whole model, from Idea to Rehearse proof

## Getting started

- [Install the CLI](/cli/install) — macOS, Linux, Windows
- [CLI product page](/cli/) — what the linter does and why

## AI plugins

- [AI plugins overview](/ai/) — all SpecScore-compatible plugins
- [SpecStudio Skills](/ai/specstudio-skills/) — opinionated SDD workflow for Claude Code
- [CLI Skills](/ai/cli-skills/) — thin CLI wrapper for Claude Code

## SpecScore for…

Role-specific guides for adopting SpecScore in your team.

- [Developers](/for/developers)
- [Product Owners](/for/product-owners)
- [Business Analysts](/for/business-analysts)
- [QA Engineers](/for/qas)
- [Project Managers](/for/project-managers)
- [Architects](/for/architects)
- [AI Agents](/for/ai-agents)

## More

- [Ecosystem](/ecosystem) — SpecScore Studio, Rehearse, Synchestra
- [Rehearse — in plain language](/rehearse) — the acceptance-evidence layer: what it does, how, and why
- [Rehearse vs. Established Testing Frameworks](/rehearse-vs-testing-frameworks) — why not just use pytest or Cucumber?
- [Blog](/blog) — articles on spec-driven development