40c1bba113
The Gitea issue body is the single source of truth for a spec; the only per-feature artifact in git is the RTM row (REQ-ID -> issue # -> test). Drops per-feature spec.md/tasks.md/checklist files from the workflow (the _example stays as a template/reference). Updates the guide, ADR-041, AGENTS.md, CLAUDE.md, templates, the RTM (adds an Issue column), the implement/review-pr skills, and replaces the file-spec CI jobs with an rtm-check. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2.7 KiB
2.7 KiB
name, about, title, labels, assignees
| name | about | title | labels | assignees | ||
|---|---|---|---|---|---|---|
| Feature (SDD spec) | Spec-driven feature request. Fill in EARS requirements before implementation starts. | As a <role> I want <capability> so <reason> |
|
Context & Why
<Who needs this and why now (2–4 sentences). Link the constitution principle(s) this depends on: .specify/constitution.md>
User Journey
<Plain-prose steps the user takes to get value, from the user's perspective. Anything not here is out of scope.>
Requirements
- REQ-001 (Ubiquitous) — The
<component>shall<always-true behavior>. - REQ-002 (Event-driven) — When
<trigger>, the<component>shall<response>. - REQ-003 (State-driven) — While
<state>, the<component>shall<behavior>. - REQ-004 (Optional-feature) — Where
<caller has Permission.X / flag set>, the<component>shall<behavior>. - REQ-005 (Unwanted-behavior) — If
<undesired condition>, then the<component>shall<safe response / ErrorCode>.
Acceptance Criteria
- REQ-001 — .
- REQ-002 — .
Out of Scope
- <The nearest tempting scope creep, named and excluded.>
API / Contract Stub
<Inline OpenAPI stub (use .specify/templates/api-contract-stub.md as a writing aid). Name new paths/methods/status codes and the @RequirePermission on each mutating endpoint.>
Data Model Changes
<Schema delta + next free Flyway V (verify on disk) + rollback note. "none" if not applicable.>
Security Considerations
<STRIDE categories touched (+ ASTRIDE if an AI agent/tool is involved). Link a threat-model.md if the attack surface is non-trivial.>
Open Questions
- — owner:
Traceability
| REQ-ID | Task ID(s) | Test ID(s) | Status |
|---|---|---|---|
| REQ-001 | Planned |
Persona Review Results
| Persona | Status | Key Findings | Resolved |
|---|---|---|---|
| Requirements Engineer | PENDING | ||
| Developer | PENDING | ||
| Security | PENDING | ||
| DevOps | PENDING | ||
| UI/UX | PENDING | ||
| Architect | PENDING |