senmu-build-projectlisted
Install: claude install-skill SenMuShare/senmu-buildos
# Project Governance
Own the governance instance, authority structure, and cross-domain ownership boundaries; this is not a parent skill. Use project entrypoints for ordinary work. Continue only for missing/conflicting governance, structural evolution, state-owner repair, or explicit governance work.
## Route by Outcome
- Create, assess, evolve governance: [Governance Instances](references/project-governance-instances-and-evolution.md).
- Staged established-project takeover: [Project Takeover](references/established-project-takeover-governance.md).
- Lifecycle, capability composition, done: [Project Practice](references/project-lifecycle-guide.md).
- Roots, layout, document ownership, maps: [Directories](references/project-directories-and-documentation.md).
- Discover/maintain effective AGENTS and on-demand standards: [Standards Discovery](references/project-standard-discovery-and-on-demand-loading.md).
- Create/select/repair cross-stage task state: [Task State](references/task-execution-and-state-management.md).
- Project situations, handoffs, skill boundaries: [Adoption and Routing](references/project-adoption-handoff-and-scenario-routing.md).
- Read [Governance Levels](references/governance-levels-and-gates.md) only for an actual G0-G4/gate decision.
Read only what the outcome needs. Delivery owns Git execution.
Use [init_project_governance.py](scripts/init_project_governance.py) for new projects and [assess_project_governance.py](scripts/assess_project_governance.py)