Loading...
Loading...
Found 6 Skills
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit without naming a narrower skill.
Governance-focused README with fixed structure and output contract. Use for asset governance, audit, or standardized first-impression docs. For process-driven creation (templates by project type) use crafting-effective-readmes.
Ask which skill or flow fits your situation. A router over the docs/Agent-Note maintenance flow, the documentation governance run, the prose-and-docs tool layer, and the standalone git and game skills in this pack.
Define team interfaces, contracts, and communication boundaries
Govern stable domain context with a narrowly scoped CONTEXT.md when needed, and route hard-to-reverse decisions to ECC's existing architecture-decision-records skill. Use when domain terms require repeated explanation, one term has multiple meanings, unclear language causes module-boundary mistakes, or domain semantics must remain separate from architecture decisions.
Audit documentation authority, reconcile conflicting specifications, and maintain canonical Single Source of Truth records across repository documentation.