magnus919_agent-skills/spec-driven-development/templates/SPEC.md

Specification: <Project / Feature Name>

Status

• Author:
• Version: 0.1.0 (draft)
• Status: Draft / Under Review / Approved
• Reviewed by:
• Gate verdict: Pending / Approved / Conditions / Rejected

Problem Statement

<One to three sentences describing the problem this specification addresses. What gap exists in the current system? What user need is unmet? Why is this worth building?>

Success Criteria

<Measurable outcomes that define success. These are NOT acceptance criteria for individual features — they are the overall outcomes justifying the investment. Example: "Reduce account creation time from 90s to under 30s.">

Scope

In Scope

Out of Scope (Explicit)

• <Capability explicitly excluded — prevents scope creep>

User Stories

US-001:

Priority: P0 / P1 / P2 / P3 Description: As a , I want so that .

Acceptance Criteria:

1. [AC-001.1] Given/When/Then or pass/fail condition
2. [AC-001.2] Given/When/Then or pass/fail condition

Edge Cases:

• <Edge case description — what happens when>

US-002:

...

Non-Functional Requirements

ID	Requirement	Threshold	Verification Method
NFR-001	Response time	< 200ms at P95	Load test
NFR-002	Availability	99.9% uptime	Monitoring
NFR-003	Security

Data Contracts & Interfaces

<Schemas, API signatures, event definitions. Stubs are acceptable at this phase — identify what contracts exist even if refined later.>

<Schema or signature>

Assumptions & Open Questions

#	Assumption / Question	Impact if Wrong	Resolution
1			<how/when resolved>
2			<how/when resolved>

Revision History

Version	Date	Author	Change
0.1.0			Initial draft