Arch Flow

---
name: arch-flow
description: "Read-only flow-status and next-step router for arch-step, miniarch-step, arch-mini-plan, and lilarch docs. Use when the user asks 'what's next?', wants a checklist, or wants the single best next move without running the workflow. Not for doing the planning or implementation work itself."
---

# arch-flow

Use this skill to inspect an existing arch-style doc and recommend the next move.

Read `references/detection.md`, `references/checklist-rules.md`, and `references/recommendation-rules.md` before building the checklist.

## When to use
- The user asks "what's next?", "where are we in the flow?", or wants a checklist.
- You want a deterministic next-step recommendation from `DOC_PATH` and `WORKLOG_PATH`, not memory.
- The doc is part of the full arch flow, the mini full-arch path, the arch-mini-plan path, or the lilarch flow.

## When not to use

- The user wants you to actually perform research, planning, implementation, or auditing. Use `arch-step`, `miniarch-step`, or `lilarch`.
- The user wants generic continuation on a full-arch doc. Use `arch-step` or `miniarch-step`.
- The user wants the concise strength/weakness status surface or wants to execute one explicit full-arch step. Use `arch-step` or `miniarch-step`.
- The doc is a bug doc or a goal-loop doc. Use the governing skill for that workflow family.

## What to do

1. Resolve `DOC_PATH` and the derived `WORKLOG_PATH`.
2. Infer whether the doc is:
   - full arch
   - mini full arch
   - arch-mini-plan follow-through
   - lilarch
3. Build a full evidence-based checklist:
   - mark each required step `DONE`, `PENDING`, `OPTIONAL`, or `UNKNOWN`
   - include the evidence note for each line
4. Recommend the single best next move:
   - `arch-step` for broad full-arch execution until the code audit is clean
   - `miniarch-step` for faster full-arch execution or post-mini-plan follow-through until the code audit is clean
   - `arch-docs` for full-arch or post-mini-plan docs cleanup after the clean code audit
   - `lilarch` for lilarch steps
5. If the user asks to run the next step, switch to the governing skill and do the work there.

## Invariants
- Use the plan doc (`DOC_PATH`) as the source of truth.
- Keep this skill read-only unless the user explicitly asks you to proceed into the next step.
- Do not invent steps or ask questions that can be answered from the repo/doc.

## Reference map

- `references/detection.md` - flow-family detection and artifact sanity checks
- `references/checklist-rules.md` - evidence-based checklist construction rules
- `references/recommendation-rules.md` - exact next-move recommendation rules by doc family