spec-writing

# Spec Writing ## Overview Spec Writing provides guidance on authoring effective `specs.md` files that drive the Sprint plugin's autonomous development workflow. A well-written specification determines the quality of agent output by clearly defining goals, scope boundaries, and testing requirements. ## Prerequisites - Sprint plugin installed (`/plugin install sprint`) - Project onboarding completed via `/sprint:setup` (creates `project-goals.md` and `project-map.md`) - Sprint directory created via `/sprint:new` (generates `.claude/sprint/[N]/specs.md`) - Understanding of the sprint phase lifecycle (see the `sprint-workflow` skill) ## Instructions 1. Open the generated `specs.md` file at `.claude/sprint/[N]/specs.md` and define a concise goal statement at the top. State what the sprint delivers in one sentence (e.g., "Add user authentication with email/password login"). 2. Define explicit scope boundaries using **In Scope** and **Out of Scope** sections. List specific features, endpoints, or components in each. Agents only implement what appears in scope; ambiguity leads to drift. 3. Add the **Testing** section to control which testing agents run and how. Configure three settings as documented in `${CLAUDE_SKILL_DIR}/references/testing-configuration.md`: - `QA`: `required` | `optional` | `skip` -- Controls API and unit test execution - `UI Testing`: `required` | `optional` | `skip` -- Controls browser-based E2E tests - `UI Testing Mode`: `automated` | `manual` -...