Accepted in its amended form on 2026-10-19 by owner decision SDLC D11, recorded in
0121.
Context
0016 rule 5 takes the spec engine from thesdlc plugin, and rule 4 fixes a spec at three documents under .agents/specs/.
That plugin carries another organisation’s naming and lives outside the repository. GitHub spec-kit gives a maintained specify, clarify, plan and tasks flow
that works with both Claude Code and OpenCode. Ad-hoc requests that skip clarification are the main source of rework. This conflicts with rules 4 and 5 of 0016.
Decision
- GitHub spec-kit is the SDLC. The
sdlcplugin is removed from the repository’s plugin set; the role names agents use stay (0017 rule 5). - A Stackra preset configures spec-kit. The constitution is generated from the docs constitution, not written twice.
- A mandatory Impact questionnaire is answered in the spec before planning: apps, services and packages touched; cross-service events; tenancy and data; secrets; Linear project; whether an ADR is needed; new dependencies.
/speckit.planrefuses until the spec is clarified and carries a Linear issue (0065).- A CI check on feature branches fails a spec whose Impact section is missing or has unanswered items.
- A prompt-hints hook nudges an ad-hoc request that looks like feature work to start at clarify.
- A Linear extension maps spec to project and plan to issues. The existing wave runner is ported.
- Spec folder layout: specs live in
.agents/specs/sta-<n>-<slug>/through a preset wrap, as decided in 0120, which also sets the lanes and the trivial-change threshold.
Consequences
- Clarification becomes a gate, not a habit; whether trivial changes may skip it, and where the threshold sits, is
TODO. - Tracking a third-party tool means upgrades through the preset, not by editing vendor files.
- Rules 4 and 5 of 0016 stop being true when this is accepted.
Enforcement
Planned: the CI spec check, the plan refusal in the preset, and theagents:check drift check of 0016. Nothing exists yet.