Archon Workflows
Runs AI workflows on a repo and answers runs that need a decision via the Archon CLI.
Install
npx skills add coleam00/Archon --skill archon-cli -g -a claude-code -y- Repository
- coleam00/Archon23.8k
- Category
- AI and agents
- Updated
- 4d ago
- License
- MIT
- Context cost
- Lightabout 1,358 tokens
- Runs scripts
- No, instructions only
What it does
Drive Archon through its CLI: run AI workflows on a repo, watch and answer the runs that need a decision, drive the SDLC pack's queues (intake, build queue, merge queue, discoveries), set up Archon or change its config, and author and validate workflows. Use when the user says "use archon", "run archon", "archon workflow", "fix issue #N with archon", "have archon review this PR", "what's running / check run <id>", "approve/reject/answer/cancel/resume that run", "run the build queue", "drain discoveries", "set up archon", "configure archon", "change my archon config", "create a workflow", "author a workflow", or asks how to write a better Archon prompt. NOT for: doing the coding work yourself. Archon delegates it to isolated runs.
Archon CLI
Archon runs multi-step AI workflows through the archon CLI. Git projects run in
isolated worktrees by default; registered folder projects run in place. You sit on
top of the runs: you write the brief, launch, watch one stream, answer the decisions
that reach you, and read what each run left behind.
Route by intent:
| The user wants to... | Read |
|---|---|
| Run a workflow on real work | operate/running.md |
| Inspect, answer, cancel or resume runs | operate/managing-runs.md |
| Drive the SDLC pack's queues | operate/queues.md |
| Find out why a run failed or hangs | operate/troubleshooting.md |
| Set up Archon or change config | setup/setup-and-config.md |
| Author or change a workflow | authoring/authoring-workflows.md (then node-reference.md and variables.md in the same folder) |
| Improve a node prompt or a run message | authoring/prompting-mistakes.md |
- When the intent is clear ("build me a workflow for X", "run archon-ship on issue #42"), go straight to the reference. Do not ask.
- When it is ambiguous, ask which of these the user wants.
- On a machine where
archon doctorfails, start withsetup/setup-and-config.md.
The operating loop
- Discover.
archon workflow list --jsongives compact descriptions. For each plausible candidate, read the full description witharchon workflow list <name> --full. Choose from full descriptions, never from names you remember. - Check the brief. The message, issue body or document the run reads is the
contract the run is measured against. It must state the problem, why it is worth
solving, why now, the desired outcome, the invariants and the acceptance. If any
is missing, say which, propose wording, and get the user's agreement before
launching.
operate/running.mdhas the full check. - Launch detached. Pass the work as a message, the workflow's declared inputs
with
--input, or both:
