Plan → Build

Drive a feature from a brief to green gates through a chain of phases where each phase's output is the next phase's input: brief → exploration → plan → vetted plan → approved plan → tested code → green gates → commit.

Two things make this workflow legible on purpose:

1. Loosely coupled. The "ticket" is a Markdown brief or an inline description, so the chain runs against your repo with no issue tracker required. Gates stay your repo's own checks; nothing calls out to CI or the cloud. (For a fully-wired example that reads Azure Boards work items and runs .NET/Make gates, see /arkandia:plan-and-build-dotnet.)
2. One phase at a time. After each phase, summarize what happened and stop. Wait for the user to say continue before starting the next phase. Make the seams visible; never run phases together. This is what makes the workflow teachable and keeps you in control of the what before the agent commits to the how.

Arguments