Dodi Dev

Use when starting work on a ticket — creates a worktree, reads ticket context, and gets you ready to implement

Fresh-context code review for any completed change — post-implementation, pre-PR in the epic lane, or child PR — with a fix loop and a Frontier-tier final round

Use after review passes when a compatibility entry point is needed; epic workflows route to dedicated PR lifecycle skills

Use before any completion claim, commit, or PR — requires running verification commands and confirming output before making success claims

Use when executing an implementation plan — dispatches subagent per task with self-review, verification along the way, and commits

Use before any feature, design, or non-trivial change — explores intent, constraints, and design before implementation

Use as the resident driver — one long-lived orchestrator session per active epic that boots from durable state, holds the dependency graph and decision-register canon in context, dispatches lanes, and advances on completion events until park, refresh-park, or bloat. Also the session-delivered coherence-ruling mode.

Use when you have a spec or requirements and need to create a step-by-step implementation plan before coding

Use when an epic worktree exists and orchestration needs to classify child tickets, dependencies, readiness, and blockers

Use after brainstorming to create a ticket in the project tracker with full context from the design session

Use when epic orchestration needs to create or resume the epic branch and worktree from the repository base branch

Use when implementation review is clean and tests must be created or completed according to the ticket Testing Contract

Use when a child ticket lacks spec-ready or ready-to-implement and needs specification, plan, review, or human input

Use when a child ticket is ready to implement and needs a child branch and worktree created from the epic branch

Execute one ready child ticket end to end in a single lane session — pickup through open child PR and child-PR review — ending at ready-to-merge-child

Open an epic PR from the epic branch to main/master and leave it open for existing GitHub Actions and review

Use when a ready child ticket has a child worktree and implementation must follow the reviewed plan exactly

Open a child ticket PR against the epic branch (lane-invoked) and merge it into the epic branch (orchestrator-invoked, serial)

Interactive epic intake through Gate 1 signoff, and the shared routing contract (state tables, worker prompts) the resident driver and manual sessions route on

Use as the scheduled janitor that converges PM ticket state with GitHub/git reality — merge transitions, deploy transitions, branch/worktree cleanup, stale claims