Arch Step

Use this skill when the user wants the real full-arch workflow and one canonical plan doc should govern it end to end.

The primary object is one canonical full-arch plan doc. Commands exist to move that doc toward a finished, internally consistent, decision-complete artifact. They are not independent mini-workflows.

When to use

• The user wants the full arch workflow for medium or large work and does not need a different workflow family.
• The ask is generic full arch language such as "do the full arch flow," "continue this architecture doc," "implement the plan," or "audit implementation against the plan."
• The work needs one canonical plan doc plus real architectural convergence onto existing repo patterns, shared code paths, or single-source-of-truth boundaries.
• The user wants explicit stage control instead of a more holistic or phase-family-driven flow.
• The ask is command-shaped: new, reformat, research, deep-dive, external-research, phase-plan, auto-plan, plan-enhance, fold-in, overbuild-protector, consistency-pass, review-gate, implement, implement-loop, auto-implement, full-auto, audit-implementation, status, or advance.
• The user wants one canonical plan driven as far as possible through planning and implementation with native goal-mode continuation.
• The user wants one specific plan-doc shape with exact headings, stable markers, and consistent stage ownership.
• The user wants advance to print the full checklist, choose exactly one next command, and optionally execute that one step.
• The user wants status to evaluate the actual plan artifact, not emit a generic checklist.

When not to use