ContextQMD
Back to Oh My Posh

Code Changes

.agents/skills/code-changes/SKILL.md

30.4.03.5 KB
Original Source

Code Changes

The workflow for going from an issue, pull request, idea, or feature request to shipped code. Follow the phases in order. Analysis always comes first; code comes last.

Each phase has a reference file with the full instructions. Read the reference file when you enter the phase — not before, and never skip it because the phase "looks obvious".

Roles

Assign work based on model capability. The coordinator is not the strongest model — it's the one that stays resident, owns every phase by default, and knows when it's out of its depth.

RoleCapability tierOwns
CoordinatorCapable mid-tier, resident for the whole taskAnalysis, plan, delegation, supervision, verification, delivery — by default
EscalationStrongest reasoning model available; invoked only on triggerThe specific judgment call the coordinator flagged, then control returns
ImplementerSame tier as coordinator, or smaller for trivial editsExecuting one pinned, self-contained task

Concrete model names per vendor (Anthropic, OpenAI, Google) and how to run the split in Claude Code, GitHub Copilot, Codex, or IDE agents: references/model-tiers.md.

When the current agent already runs at implementer tier, there's no separate delegation step for standard work: plan and execute directly, still following every phase. Escalate to the strongest model only when a trigger fires — see references/escalate.md — never by default and never for a routine judgment call the coordinator is equipped to make itself.

The flow

  1. Analyze (references/analyze.md) — root cause and scope, validated against the code, never against the report alone.
  2. Plan (references/plan.md) — pinned spec, task split, parallel vs sequential, workspace per task.
  3. Delegate (references/delegate.md) — match each task to the right executor, coordinator-tier by default.
  4. Supervise (references/supervise.md) — monitor, unblock, and critically review implementer output.
  5. Verify (references/verify.md) — quality gates plus functional proof, never delegated downward.
  6. Deliver (references/deliver.md) — conventional commits and an outcome-first report.

Analyze, Supervise, and Verify each carry an escalation checkpoint — see references/escalate.md — for handing one specific judgment call to the strongest available model without giving up ownership of the phase.

Stop gate: Phase 1 ends with reporting the analysis and proposed approach to the user and waiting for a go. Skip the gate only when the user already gave the go in the request itself ("do it", "fix it and commit", "implement with Sonnet").

Special cases

These entry points replace or extend Phase 1; the rest of the flow applies unchanged.