HankLiu447
Publisher on askill
Use when about to claim work is complete, fixed, or passing. REQUIRES running verification commands and confirming output before making any success claims. Evidence before assertions, always.
Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification, not performative agreement or blind implementation.
Use when implementing any feature or bugfix, before writing implementation code. Each Scenario in Specs becomes a test case following RED → GREEN → REFACTOR cycle.
Use when you have a written implementation plan to execute in a separate session with review checkpoints. Alternative to subagent-driven development for batch execution.
Execute Gemini CLI for AI-powered code analysis and generation. Use when you need to leverage Google's Gemini models for complex reasoning tasks.
Use to validate spec documents for correctness, completeness, and consistency. Ensures specs follow SuperSpec format and are ready for implementation.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. Dispatch one agent per independent problem domain for parallel execution.
Execute Codex CLI for code analysis, refactoring, and automated code changes. Use when you need to delegate complex code tasks to Codex AI with file references (@syntax) and structured output.