Name: Skill Governance
Author: pek007

Govern the skill portfolio as an architectural layer, not a loose collection of prompt folders.

Do

Classify the skill as shared-platform, product-capability, or transitional-local.
Check ownership, review path, lifecycle state, and readiness.
For product-capability skills, verify:
- owning product
- capability ID
- delivery mode rationale
- evidence path
Decide whether skill is actually the right delivery mode.
Recommend the next lifecycle move:
- create
- approve
- build
- test
- activate
- improve
- constrain
- retire
Keep the skill narrow; split mixed-purpose skills where needed.
Keep SKILL.md lean and move detailed material into references/ or scripts/ when justified.
Update the registry and linked capability records when promotion or status changes occur.

Evaluate with these questions

Govern the skill portfolio as an architectural layer, not a loose collection of prompt folders.

Classify the skill as shared-platform, product-capability, or transitional-local.
Check ownership, review path, lifecycle state, and readiness.
For product-capability skills, verify:
- owning product
- capability ID
- delivery mode rationale
- evidence path
Decide whether skill is actually the right delivery mode.
Recommend the next lifecycle move:
- create
- approve
- build
- test
- activate
- improve
- constrain
- retire
Keep the skill narrow; split mixed-purpose skills where needed.
Keep SKILL.md lean and move detailed material into references/ or scripts/ when justified.
Update the registry and linked capability records when promotion or status changes occur.