Guides authoring specs.md files for Sprint plugin sprints: goal statements, in/out scope boundaries, testing configs (QA/UI modes) for agentic development.
From sprintnpx claudepluginhub nickloveinvesting/nick-love-plugins --plugin sprintThis skill is limited to using the following tools:
references/errors.mdreferences/examples.mdreferences/testing-configuration.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides slash command development for Claude Code: structure, YAML frontmatter, dynamic arguments, bash execution, user interactions, organization, and best practices.
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.
/plugin install sprint)/sprint:setup (creates project-goals.md and project-map.md)/sprint:new (generates .claude/sprint/[N]/specs.md)sprint-workflow skill)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").${CLAUDE_SKILL_DIR}/references/testing-configuration.md:
QA: required | optional | skip -- Controls API and unit test executionUI Testing: required | optional | skip -- Controls browser-based E2E testsUI Testing Mode: automated | manual -- Auto-run or user-driven testingrequired for new API endpoints, business logic changes, and data validation rules. Set QA to skip for frontend-only changes, documentation updates, or configuration changes.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.backend-specs.md, frontend-specs.md, api-contract.md). Over-specifying implementation details in specs.md constrains the architect unnecessarily.status.md from the previous iteration. Remove completed items from specs and add any new requirements or bug fixes discovered during testing.specs.md file with goal, scope (in/out), and testing configuration| Error | Cause | Solution |
|---|---|---|
| Agents implement unintended features | Missing "Out of Scope" section | Explicitly list features excluded from this sprint |
| Tests not running during sprint | Testing section omitted or set to skip | Add QA: required and UI Testing: required to the Testing section |
| Sprint iterates without converging | Specs too broad for a single sprint | Break into smaller sprints targeting one domain boundary each |
| Architect produces conflicting spec files | Ambiguous or contradictory requirements in specs.md | Review for conflicting statements; each requirement should have a single interpretation |
| Manual tests not triggered | UI Testing Mode set to automated | Change to manual for scenarios requiring visual verification or exploratory testing |
Minimal but effective spec:
# Sprint 1: User Authentication
## Goal
Add user authentication with email/password login
## Scope
### In Scope
- Registration endpoint (POST /auth/register)
- Login endpoint (POST /auth/login)
- JWT token generation and validation
- Password hashing with bcrypt
### Out of Scope
- OAuth providers (Google, GitHub)
- Password reset flow
- Email verification
## Testing
- QA: required
- UI Testing: required
- UI Testing Mode: automated
Frontend-only sprint (no QA needed):
# Sprint 3: Dashboard Redesign
## Goal
Redesign the admin dashboard with responsive layout
## Scope
### In Scope
- Responsive grid layout for dashboard widgets
- Dark mode toggle
- Mobile navigation drawer
### Out of Scope
- New API endpoints
- Database changes
- Authentication changes
## Testing
- QA: skip
- UI Testing: required
- UI Testing Mode: manual
${CLAUDE_SKILL_DIR}/references/testing-configuration.md -- Testing section options with guidance on when to use each setting