Files
familienarchiv/.gitea/ISSUE_TEMPLATE/feature.md
Marcel 2dd7e33aad feat(sdd): add Gitea issue templates and SDD CI gate
Adds .gitea/ISSUE_TEMPLATE/{feature,bug}.md (the feature template mirrors the
EARS feature-spec) and .gitea/workflows/sdd-gate.yml — spec-lint, contract
validation (Spectral), traceability check (all non-blocking during adoption),
and a constitution-impact PR comment.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-13 11:56:37 +02:00

2.7 KiB
Raw Blame History

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>
spec-required
needs-review

Context & Why

<Who needs this and why now (24 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 stub or link to .specify/features//api-contract.yaml. 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