Skill reference

Read detailed public profiles generated from canonical Adaptive Skills contracts.

Use these profiles when the catalog summary is not enough to decide how a skill works, what it returns, or how to verify the result.

Each profile is generated from its canonical skills/<name>/SKILL.md file. The public page adds orientation and navigation, but it does not replace or independently rewrite the contract.

Complete reference

Skill	Category	Use it when
`workflow`	Engineering	Starting non-trivial work or returning from a handoff
`feature-planning`	Engineering	Turning a feature request into staged delivery
`testing`	Engineering	Choosing proof before closing meaningful work
`debugging`	Engineering	Investigating a reproducible failure
`api-design`	Engineering	Defining a contract between components
`refactoring`	Engineering	Improving structure without changing behavior
`lean-implementation`	Engineering	Implementing a confirmed bounded plan
`architecture-review`	Engineering	Reviewing a consequential structural decision
`code-style`	Engineering	Improving consistency and readability
`communication`	Engineering	Explaining a change, failure, option, or handoff
`domain-language-alignment`	Engineering	Product, domain, docs, and code use different terms
`ux-strategy`	Design	The interaction direction is still open
`ux-provocation`	Design	A dominant UX hypothesis needs pressure testing
`heuristic-audit`	Design	An existing interface has usability risks
`ux-writing`	Design	Product language is unclear or unsafe
`design-system-intelligence`	Design	Reviewing an artifact against declared design-system sources
`experience-design`	Design	A broad experience request needs selective composition
`documentation`	Documentation	Creating, restructuring, or auditing onboarding, manuals, guides, and technical documentation
`intent-clarification`	Planning	Outcome, success, or constraints are ambiguous
`premortem`	Planning	A consequential plan could fail in costly ways
`task-chunking`	Efficiency	Work is oversized or likely to sprawl
`checkpoint-review`	Efficiency	A long task needs a continue-or-stop decision
`handoff-summary`	Efficiency	Work is crossing a person, agent, or session boundary
`work-continuity-efficiency`	Efficiency	A broad continuity need requires selective composition
`triad-check`	Cross-functional	A hard-to-reverse decision crosses product, design, and engineering
`product-management`	Product	A product request spans framing, evidence, method selection, outcomes, or handoffs
`feature-value-governance`	Product	Deciding whether a feature deserves investment
`opportunity-tree-alignment`	Product	Backlog bets lack clear outcome links
`business-design`	Business	Framing product or business strategy from mixed signals
`revenue-lever-mapping`	Business	A value claim has no measurable mechanism
`feature-complexity-audit`	Governance	Permanent feature cost may change a build decision
`sunset-decision`	Governance	An existing feature may no longer justify its cost
`knowledge-source-evaluation`	Governance	A document may become governed knowledge
`knowledge-conflict-resolution`	Governance	Decision-relevant sources disagree
`restricted-context-check`	Governance	Sensitive or untrusted knowledge may enter task context
`knowledge-governance`	Governance	A broad source-governance decision needs selective composition
`qa-review`	Quality	A change needs a cross-layer quality gate
`observability-review`	Metrics	Metrics, events, alerts, or diagnostics need review

The skills catalog provides the same complete inventory with expected outcomes for faster selection.

What each profile includes

the canonical description, category, version, and owner
direct navigation to usage, restrictions, core moves, outputs, and verification
the complete skill contract
an explicit link to the source file

Public profiles are a reader-facing projection. They do not change skill behavior, routing authority, or runtime execution.