archflow-status git:20260911.a26fb9fA

Immutable. This exact content is served forever at /api/v1/blob/bc05ed9baf97e80d.

---
name: archflow-status
description: "Where the project stands: phase, mode, active release, and what to run next"
---

> Invoke with `$archflow-status`. Arguments are the text after the mention.


# $archflow-status — Project status + available commands

## Step 1 — Project status

Read `.archflow/current-phase.yaml` and `.archflow/project-settings.yaml` if they exist, and report:
- current phase + `phase_file`
- `project_type`
- `mode` (quick | full)
- design system: from `.archflow/design-system.yaml` — `{design_system} ({platform} · {library})`, or
  `not set — run $archflow-design` when the project has a UI and the file is missing
- `active_release` (and, from `.archflow/releases/{active_release}.yaml`, its progress: stories done / total)
- open blocking issues: any story in the active release with an `issues[]` entry that is
  `status: open` and `severity: blocking`, as `{story-id} — {n} open blocking`. Omit the line when
  there are none. These are review findings that stop a story reaching `done`, and nothing else
  surfaces them.
- what is sensible to run next (see the command list below)

Edge cases:
- If `.archflow/roadmap.yaml` is v1.0 (has `phases:` / no `schema_version`): suggest `$archflow-migrate`.
- If `.archflow/current-phase.yaml` is missing: `No project onboarded. Run $archflow-onboard (existing codebase) or $archflow-init (new project) to get started.`

## Step 2 — Available commands

```
Archflow — Phase-Based Development Workflow

  $archflow-status        This screen — current phase, active release, what to run next

  $archflow-init          Initialize Archflow in a new project
                          (creates .archflow/ state files, sets Phase 1)

  $archflow-onboard       Onboard an existing codebase to the phase framework
                          (detect project type, import context, audit, set phase)

  $archflow-migrate       Migrate a v1.0 project to schema v2.0
                          (releases replace phases, sprints retired, multi-file split)

  $archflow-mode          Show or switch the ceremony mode (quick | full)

  $archflow-release       Inspect / manage releases (status, new, start, ship)

  $archflow-setup-mcp     Configure MCP servers for external tools
                          (Jira, Notion, Linear, GitHub, SuperDesign, etc.)

  $archflow-groom         Detail or refine a story — a backlog stub, or one already in a
                          release (re-derives its gates)
                          (acceptance criteria, subtasks, gates — stays in the backlog)

  $archflow-feature       Add a story — to the backlog, or straight into the active release
                          (from description, external tool link, or existing backlog stub)

  $archflow-autopilot     Run queued release stories unattended on one branch
                          (blocker interview first, then silent; one report at the end)

  $archflow-design        The project's design system, or one story's screens
                          ($archflow-design S7-20 clears that story's design gate)
                          (chosen once per project; every UI agent builds against it)

  $archflow-contract      The API contract architecture, or one story's endpoints
                          ($archflow-contract S7-20 clears that story's contract gate)

  $archflow-issue         Record a defect on a story being built, list what is open, or
                          defer a minor one to the backlog
                          (the only sanctioned way to defer — no agent may)

  $archflow-doctor        Check the environment and project state — what is missing and
                          how to fix it (--validate checks state files against schemas,
                          --fix repairs drift after a plugin upgrade)

  $archflow-studio        Open Archflow Studio, a local web workspace over these files
                          (beta — stop | status | port <n>)
```