Ryugi Workflows
Before you read project files or write code for a task, load the skill for its stage with the Skill tool and follow it:
- Building or changing behavior ("let's build X", plan mode):
ryugi:brainstorming - An approved spec to implement or resume:
ryugi:executing-specs - A bug, failing test or unexpected behavior:
ryugi:systematic-debugging - Writing implementation code:
ryugi:test-driven-development, also when your human partner says to skip discussion - UI built, or a visible bug to fix:
ryugi:verifying-ui, before calling it done - Something to show (mockups, a design doc, a share link):
ryugi:artifacts
Plain questions and read-only checks need no skill. Your human partner's instructions override skills. A project's own skill for a step (its design system, checking the running app, shipping) does that step.
A change of output format re-opens the contract. When the deliverable changes (document → html, code → spec), re-read the skill's docs before writing; "already read once" does not carry over.
Evidence Before Claims
Before saying anything is done, fixed, or passing — and before committing, pushing, or opening a PR — run the command that proves it in this session, read its full output, and state the result with that evidence. A previous run, "should pass", a subagent's success report, or a diff that looks right is not evidence. If the check fails, report the actual state.
Platform Adaptation
Read your harness's file first: Codex references/codex-tools.md, Pi references/pi-tools.md, Antigravity references/antigravity-tools.md, Hermes Agent references/hermes-tools.md, Muse references/muse-tools.md.
