# experimplate — authoring plan (JIT, next session)

> The standalone, reusable project-workflow template extracted from spt-core's working style.
> Sole user: the operator. First consumer: `spt-claude-code`. Decisions: see
> `../spt-claude-code/SCOPE.md` (Q2/Q3/Q8 + "experimplate resolved content").

## Goal
A skeleton repo a new project instantiates to inherit spt-core's proven workflow: traceable-reqs
gating, JIT plans, grill-with-docs underbelly, release+changelog discipline, same-repo published
docs (with spt-core's docs theme), harness-agnostic instructions. Copy-as-template, scrubbed —
NOT re-authored. The scaffolding is meta-process, so copying it does NOT violate a consumer's
"public-surface-only" constraint.

## Files to author
1. **AGENTS.md** — canonical working rules (source of truth). Scrub spt-core specifics →
   placeholders (`<PROJECT>`, `<orientation docs>`). Carry: traceability rules (tag-in-same-commit,
   check-before-done, REQ-first, hazards-as-REQs, activate-don't-pre-fail), commit-trailer rule,
   match-surrounding-style, dual-audience docs note, JIT-plan + self-clear/commune close-out rule.
2. **CLAUDE.md** — one line: `@AGENTS.md` + a stub for CC-only extras. (CC reads CLAUDE.md only;
   import bridges AGENTS.md. Other harnesses read AGENTS.md direct.)
3. **traceable-reqs.toml** — empty registry seed + `[scan].roots` placeholder + `[policy]`
   required_stages=[]. Header comment: activation model + how to ACQUIRE traceable-reqs
   (gh release download BigscreenVR/traceable-reqs ...) + the four-stage contract.
4. **docs/TRACEABILITY.md** — the contract, scrubbed (copy from spt-core/docs/TRACEABILITY.md).
5. **docs/DOCS-STRATEGY.md** — reframed SAME-REPO docs→GH Pages (vs spt-core's separate
   spt-releases split). mdBook + reuse spt-core docs theme CSS/layout (transferable styling).
6. **docs/KNOWN-HAZARDS.md** — skeleton + the hazard-as-REQ-HAZARD-* pattern explainer.
7. **docs/RELEASE-RUNBOOK.md** — GENERIC release shape + placeholders: CHANGELOG · version bump ·
   tag · GH Release on same repo · docs-gen→GH Pages CI gate. Project fills publish specifics.
8. **CONTEXT.md** — glossary stub (grill-with-docs convention; authoritative for meaning).
9. **docs/adr/** + **docs/formats/** (ADR + CONTEXT/ADR format guides — copy from grill-with-docs skill).
10. **CI** — agent-driven autonomous pattern (no LLM-in-loop; deterministic gates; spt reporting
    bus; git-hook trigger). Document as the default; GH-runner optional.
11. **INSTANTIATE.md** — how to stand up a new project from the template: clone/copy, fill
    placeholders, ACQUIRE traceable-reqs (install steps) + the grill-with-docs skill (where to get
    it / install), wire CI, first `traceable-reqs check`. The one-stop bootstrap doc.
12. **docs theme** — bring spt-core's mdBook theme CSS/layout as a shared asset (strong styling,
    transfer across projects). Pull from spt-core/docs-site.

## Then
- Instantiate `spt-claude-code` FROM experimplate (re-home SCOPE.md/CONTEXT.md onto the structure).
- Write `spt-claude-code/HANDOFF.md` for perri (public-surface-only constraint up front + M12 gate).
- Both gated on full-fat M12 shipping (todlando) before perri begins.

## Notes
- git initialized; `docs/adr` + `docs/formats` dirs exist (empty).
- Don't over-engineer the instantiate mechanism — documented skeleton + INSTANTIATE.md for v1;
  a bootstrap script is a later nicety.