Trevoke

Use EVERY TIME you need to run tests, verify tests pass, or check for regressions. ALWAYS use this instead of running eldev directly.

Use when code quality needs improvement after implementation, without changing behavior

Use when implementation is complete and you want to verify quality through adversarial testing that writes code and provides evidence

Use when a design exists and it's time to break it into tasks and execute with subagent dispatch and review

Use when requirements exist and a technical design is needed before implementation begins

Use when a new feature request, bug report, or work request needs requirements defined before implementation

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

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

Use when starting new feature work to turn ideas into fully formed designs through collaborative dialogue

Use after implementation to review code against spec and quality standards

Use when an implementation plan exists and needs to be broken into parallelizable work units with dependencies

Use when bead implementation is complete and ready for integration

Use when executing a single bead/task with test-driven development approach

Use when a design document exists and needs to be broken into detailed implementation tasks