spec-writing

name	spec-writing
description	Execute this skill should be used when the user asks about "writing specs", "specs.md format", "how to write specifications", "sprint requirements", "testing configuration", "scope definition", or needs guidance on creating effective sprint specifications for agentic development. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
allowed-tools	Read
version	1.0.0
author	Damien Laine <[e-mail]>
license	MIT
compatible-with	claude-code, codex, openclaw
tags	["community","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 -- Auto-run or user-driven testing
4. Set QA to required for new API endpoints, business logic changes, and data validation rules. Set QA to skip for frontend-only changes, documentation updates, or configuration changes.
5. Set UI Testing to required for user-facing features, form submissions, and navigation flows. Choose automated mode for regression testing and standard CRUD flows; choose manual mode for complex interactions, visual verification, or exploratory testing.