ICODE · Claude Code · Codex · CodeBuddy · WorkBuddy
AI coding workflow: from request to verification evidence
ICODE turns a development request into a ticket that can be inspected, paused and resumed. It does not replace your host agent; it adds explicit stages, stop points and evidence boundaries to the existing session.
Bind the real project and its boundaries
Run /icode start from the project session, confirm the requested path and actual Git root, then create the ticket. State the goal, exclusions and stop point so the skill repository is never mistaken for the product repository.
Separate design, review and implementation
Planning, design review, finalization and coding leave separate artifacts. Implementation follows the finalized plan and current source; a scope change returns to the relevant gate instead of silently replacing the ticket contract.
Make verification match real evidence
Use /icode verify to select build, deploy, listen or test explicitly. Listen or test alone uses the version already on the device and never implies a build or deployment. Missing devices and tools remain visible verification debt.
Keep one workflow across hosts
Claude Code, Codex, CodeBuddy and WorkBuddy use the same ICODE step contracts. You may change host or model, but ticket state, authorization boundaries and evidence requirements remain intact.
Commands
/icode start Add retries to the existing module and cover them with tests/icode verify --build --deploy --test <target>Examples explain workflow behavior; they are not execution evidence.