using-agent-skills

Identify the development phase your task belongs to, then follow the decision tree: new features route to spec-driven-development, bugs route to debugging-and-error-recovery, and reviews route to code-review-and-quality. When in doubt, start with a spec.

A meta-skill governs how all other skills are discovered and invoked. It contains no implementation logic itself but provides routing rules, lifecycle sequencing, and shared operating behaviors that apply across every skill.

Yes. A feature implementation typically chains skills in sequence, such as spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, and code-review-and-quality. A bug fix may only need two or three.

Skill discovery should run before any non-trivial work begins. Only trivial tasks with no ambiguity can skip it, since skills encode verification steps that prevent common failure modes like unchecked assumptions.

Six behaviors apply at all times: surface assumptions, manage confusion actively, push back when warranted, enforce simplicity, maintain scope discipline, and verify results with evidence rather than assuming correctness.