open-agent

Use when executing plans through specialized subagents with evidence-gated review loops

Use when work needs an explicit delivery contract, iterative repair, bounded autonomy, or resume-safe state

Use when a user asks to continue, resume, pick up prior loop work, or inspect previous loop state

Use when work needs codebase orientation, impact analysis, existing-pattern discovery, or risk scouting before planning or implementation

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 implementation direction depends on unresolved product/design choices, multiple viable approaches, or owner approval on a design.

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

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

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 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 you have a spec or requirements for a multi-step task, before touching code

Use after a loop ships or after verify fails repeatedly at budget — captures failure patterns and improvement candidates so the next loop starts smarter

Use after implementation is verified and before merge — consolidates multiple spec iterations into a single final-state report, marks related specs, and records key lessons

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

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 completing tasks, implementing major features, or before merging to verify work meets requirements

Use whenever you need a decision, clarification, or approval from the user — covers how to ask with the question tool, and how to resolve the decision yourself when no user is available (question tool absent, or a [Never-Ask] response)

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

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies