regenerate-readme

# Skill: Regenerate README > Sentinel: `TASKBOARD-SKILL-REGENERATE-README`. Echo this string in your first reply when the orchestrator probes whether the skill loaded. Rebuild [`README.md`](../../../README.md) from the current product reality. README is a narrative document; it drifts whenever code, architecture, or tone changes. This skill captures the contract so the regeneration is repeatable. ## When to invoke - After a load-bearing change to runner / orchestrator / supervisor / skill model that the README must reflect. - After a marketing-tone refresh. - When a periodic system review flags README drift against ROADMAP.md or AGENTS.md. ## Inputs The README must stay in sync with these sources of truth. Read them first; never paraphrase from memory: - [`ROADMAP.md`](../../../ROADMAP.md) - product thesis, themes, hard boundaries. - [`AGENTS.md`](../../../AGENTS.md) - architecture pointers, orchestration philosophy, supervision model. - [`docs/system/architecture/decisions/adr-archive.md`](../../../docs/system/architecture/decisions/adr-archive.md) - load-bearing decisions to honour. - [`docs/quality/design-principles.md`](../../../docs/quality/design-principles.md) - UX contract. - [`docs/system/contracts/protocol-style.md`](../../../docs/system/contracts/protocol-style.md) - Activity Log shape. - [`backend/Endpoints/EndpointMapping.cs`](../../../backend/Endpoints/EndpointMapping.cs) - the actual route surface; never invent endpoints. ## Hard rules These are policy...