Skill Principles

To enforce consistent skill governance, align authors with shared principles requiring concise intent statements, in/out scope definitions, and mode selections before authoring begins. This prevents ad hoc directives and ensures reusable guidance across CLI-operational skills.

Skill governance principles are a shared mental model for skill creation. You need them when creating or updating CLI-operational, tool, or practice skills to ensure reliable output expectations, convergence patterns, and consistent scope boundaries rather than one-off directives.

Document scope boundaries and retirement criteria by defining intent, convergence patterns, output expectations, and promotion-retirement criteria before syncing changes. This lifecycle governance ensures mandatory referencing of supporting skills when evolving the system.

Yes, your CLI skill needs convergence patterns and output expectations documented to enforce decision hygiene. This keeps agent choices repeatable by applying selector-first, human-first CLI norms before a skill is registered.

The best way to avoid ad hoc directives is applying a shared governance layer that demands documenting intent, scope boundaries, and output expectations. This meta-level review process ensures every new practice skill carries reusable guidance.

You should avoid using a shared governance layer for trivial, one-off tasks that do not require reusable guidance or CLI-readiness. It is designed for meta-level reviews of evolving skills where consistent scope boundaries and retirement criteria are necessary.