cf-powers

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

Use when you have a spec for a non-trivial task with non-obvious sequencing, multiple coordinated files, or unclear ordering of steps. SKIP when the task is mechanical (add one file, edit a config, one-liner) or when the implementation order is obvious from the request.

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

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

Use for non-trivial implementations involving design choices, multiple components, or unclear requirements. Explores ideas through dialogue, then produces a technical analysis with architecture, phases, risks, and cross-check reviews. SKIP for mechanical/single-file changes (Dockerfile, CI YAML, config tweak, one-liner) or when the user has already specified exactly what to build.

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

Use when implementation of a feature, fix, or refactor is finished, before claiming work complete or starting merge/PR — any change that may affect docs/, README, CHANGELOG, or inline docstrings/JSDoc

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 reviewing a technical analysis, design document, or specification from a business analyst perspective - checking requirements completeness, user workflows, edge cases, and business logic

Use when reviewing a technical analysis, design document, or specification from a developer perspective - checking technical feasibility, architecture, integration points, and performance/security

Use when reviewing a technical analysis, design document, or specification from a performance perspective - checking missing indexes, N+1 queries, algorithm complexity, memory usage, caching strategy, and scalability

Use when reviewing a technical analysis, design document, or specification from a security perspective - checking attack vectors, trust boundaries, authentication, data integrity, and fail-safe behavior

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