docs: make specs/plans git-tracked and transient — retired via git rm at cycle close

docs/specs and docs/plans hold only the active cycle's artefacts: a spec/plan is committed while its cycle is live and git-rm'd in the cycle-close commit (after audit drift-clean), so HEAD shows only in-flight work while git history keeps the full text. No issue-posting, no gitignore branch — git history + the design ledger are the durable record. Rewrites conventions.md § Lifecycle as the single source of truth; pipeline.md, design.md, README.md, specify, planner, glossary, brainstorm, issue, and the CLAUDE.md fragment follow it. Naming stays NNNN-slug.md (a within-cycle handle; recycling on an emptied directory is fine).
2026-06-18 11:59:45 +02:00
parent c5da79f8fc
commit 012e70b058
10 changed files with 68 additions and 13 deletions
@@ -362,7 +362,9 @@ return here. Only proceed after approval AND a fresh Step 5 PASS.

 The orchestrator commits the approved spec after sign-off (suggested
 commit subject: `spec: <cycle> <topic>`). The skill does not perform
-the commit itself.
+the commit itself. The spec is an ephemeral active-cycle artefact: it
+lives in the repo only for its own cycle and is `git rm`'d at cycle
+close (see `docs/conventions.md` § Lifecycle).

 **In `/boss` (autonomous):** `specify` is dispatched autonomously —
 it is bounded (no interview). It runs the criterion, parse, and