wukong-code

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when implementing any feature or bugfix, before writing implementation code

Use when executing implementation plans with independent tasks in the current session

Use when creating new skills, editing existing skills, or verifying skills work before deployment

You MUST use this before creative or behavior-changing work — creating features, building components, adding functionality, modifying behavior, or ambiguous product intent. Explores user intent, requirements and design before implementation.

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

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

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

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when completing tasks, implementing major features, or before merging to verify work meets requirements