@sriray
score
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
@sriray
score
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
@sriray
score
Use when you have a written implementation plan to execute in a separate session with review checkpoints
@sriray
score
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
@sriray
score
Use when executing implementation plans with independent tasks in the current session
@sriray
score
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
@sriray
score
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Page 1 of 1 (7 skills)