template-retarget

Skill: template-retarget

Use when repurposing the repository template to a new product or domain while preserving the factory operating system.

Loop

1. Start with AGENTS.md, docs/runbooks/current-worktree-loop.md, docs/references/template-retargeting.md, and docs/references/repo-bootstrap-for-new-product.md.
2. Open or update the request, RFC when required, and one active plan before changing living product truth.
3. Rewrite tooling/template-retargeting.config.json first so the active project contract, seed baseline, routes, domains, and reference paths are explicit.
4. Replace product docs, domain inventory, routes, observability contracts, and quality coverage in the same delivery unit.
5. Keep browser proof, observability proof, data-pipeline validation, and process validation intact; add validators instead of weakening constraints.
6. Run npm run task:verify-current before publication.

Guardrails

• Do not treat completed plans, requests, RFCs, or ADRs as living product truth.
• Do not introduce a helper that decides strategy or launches Codex non-interactively.
• Use deterministic scripts only for scaffolding, validation, or metadata sync.