Two additions from researching AWS Kiro and BMAD-METHOD against cad's ADR-0002 direction:
EARS-lite acceptance criteria (Kiro pattern) — spec-driven-dev/feature-spec currently do prose success criteria only. Add an EARS-lite section (formal, near-machine-checkable phrasing: "WHEN <trigger> THE SYSTEM SHALL <response>") as an option alongside prose, not a replacement — closes the requirements half of cad's audit trail, which today is Gitea-issue-body prose only.
Inline context snapshot (BMAD pattern) — BMAD's Scrum-Master-agent step compiles hyper-detailed story files with full architectural context embedded inline, not just linked. Add a step to feature-spec (or wherever the executor-facing handoff happens) that snapshots relevant architecture/ADR context into the spec itself, so the executor doesn't have to re-derive it from a reference.
Ref: cad research fork verdict (2026-07-25).
Two additions from researching AWS Kiro and BMAD-METHOD against cad's ADR-0002 direction:
1. **EARS-lite acceptance criteria** (Kiro pattern) — `spec-driven-dev`/`feature-spec` currently do prose success criteria only. Add an EARS-lite section (formal, near-machine-checkable phrasing: "WHEN \<trigger\> THE SYSTEM SHALL \<response\>") as an option alongside prose, not a replacement — closes the requirements half of cad's audit trail, which today is Gitea-issue-body prose only.
2. **Inline context snapshot** (BMAD pattern) — BMAD's Scrum-Master-agent step compiles hyper-detailed story files with full architectural context embedded inline, not just linked. Add a step to `feature-spec` (or wherever the executor-facing handoff happens) that snapshots relevant architecture/ADR context into the spec itself, so the executor doesn't have to re-derive it from a reference.
Ref: cad research fork verdict (2026-07-25).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two additions from researching AWS Kiro and BMAD-METHOD against cad's ADR-0002 direction:
spec-driven-dev/feature-speccurrently do prose success criteria only. Add an EARS-lite section (formal, near-machine-checkable phrasing: "WHEN <trigger> THE SYSTEM SHALL <response>") as an option alongside prose, not a replacement — closes the requirements half of cad's audit trail, which today is Gitea-issue-body prose only.feature-spec(or wherever the executor-facing handoff happens) that snapshots relevant architecture/ADR context into the spec itself, so the executor doesn't have to re-derive it from a reference.Ref: cad research fork verdict (2026-07-25).