skill-selection.md

name	skill-selection
description	Decision guide for selecting the appropriate process skill based on context. Routes agents to the correct skill when starting work or when context is ambiguous.
summary	1. Check if PR feedback exists → receiving-code-review 2. Check if bug/unexpected behavior → systematic-debugging 3. Check if ticket exists → No: requirements-gathering 4. Check if requirements clear → No: brainstorming 5. Check if plan exists → No: writing-plans 6. Check if code ready → Yes: test-driven-development 7. Check if claiming done → verification-before-completion
triggers	no ticket exists for this work ticket exists but requirements unclear ready to plan implementation encountered unexpected behavior or bug received feedback on pr or code review claiming work is complete which process skill should i use requirements or brainstorming skill selection needed which workflow applies

Skill Selection Playbook

Overview

This playbook guides agents to the correct process skill based on current context. It addresses the skill selection loophole where agents may load the wrong skill for their situation (e.g., brainstorming when requirements-gathering should apply).

Decision Tree

flowchart TD
    Start[Evaluate Context] --> PR{PR feedback<br>received?}
    PR -->|Yes| RCR[receiving-code-review]
    PR -->|No| Bug{Bug or unexpected<br>behavior?}
    Bug -->|Yes| SD[systematic-debugging]
    Bug -->|No| Ticket{Ticket<br>exists?}
    Ticket -->|No| RG[requirements-gathering]
    Ticket -->|Yes| Reqs{Requirements<br>clear?}
    Reqs -->|No| BS[brainstorming]
    Reqs -->|Yes| Plan{Plan<br>exists?}
    Plan -->|No| WP[writing-plans]
    Plan -->|Yes| Code{Code<br>ready?}
    Code -->|Yes| TDD[test-driven-development]
    Code -->|No| Done{Claiming<br>done?}
    Done -->|Yes| VBC[verification-before-completion]
    Done -->|No| Clarify[Prompt for clarification]

Loading

Priority Rules

Rules are evaluated in order. First matching condition determines the skill.

Priority	Precondition	Recommended Skill
P1	PR review feedback received	receiving-code-review
P2	Bug/unexpected behavior	systematic-debugging
P3	No ticket exists for new work	requirements-gathering
P4	Ticket exists, requirements unclear	brainstorming
P5	Ticket exists, ready to plan	writing-plans
P6	Implementation plan exists, code ready	test-driven-development
P7	Work complete, claiming done	verification-before-completion

Edge Case Handling

Multiple Conditions Match

When multiple conditions match simultaneously, use priority order:

• P1 beats all others (PR feedback takes precedence)
• P2 beats P3-P7 (debugging takes precedence over workflow)
• Earlier priority always wins

Example: Bug reported + no ticket exists

• P2 (systematic-debugging) wins over P3 (requirements-gathering)
• Fix the bug first, then create ticket if needed

User Explicitly Requests Skill

When user explicitly says "use X skill":

• Defer to user's choice
• Provide recommendation as advisory only
• Do not override explicit requests

No Conditions Match

When context is ambiguous:

• Do not make arbitrary recommendations
• Prompt user for clarification
• Ask: "What are you trying to accomplish?"

Quick Reference

Situation	Use This Skill
PR has reviewer comments	receiving-code-review
Test failing, unexpected error	systematic-debugging
New feature request, no ticket	requirements-gathering
Ticket exists, reqs are fuzzy	brainstorming
Ticket ready, need implementation	writing-plans
Plan approved, time to code	test-driven-development
Code done, about to mark complete	verification-before-completion

Common Mistakes

Mistake 1: Brainstorming Without Ticket

Wrong: User asks for new feature → load brainstorming Right: User asks for new feature → load requirements-gathering (create ticket first)

Mistake 2: Ignoring PR Feedback

Wrong: PR feedback exists → continue with TDD Right: PR feedback exists → load receiving-code-review (address feedback first)

Mistake 3: Skipping Verification

Wrong: Code complete → mark done Right: Code complete → load verification-before-completion (verify first)

See Also

• skills/process-skill-router/SKILL.md - Detailed routing skill
• skills/requirements-gathering/SKILL.md - Creating tickets
• skills/issue-driven-delivery/SKILL.md - Work item lifecycle