Files
AirCoding/AirPlan/docs/spec/AirPlan-ParaV2/plugins/airarc/commands/airarc.md
AirCoding ae44be31d5 chore: push all design docs, V2 plan specs, and current working state
Includes AirPlan design documents, AircOding-alpha1-plan, AirPlanV2,
AirPlan-ParaV2, AirPlan-Para V1 reference docs, and all working code
changes across packages.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-06-12 17:12:29 +08:00

1.4 KiB
Executable File

description, argument-hint, allowed-tools
description argument-hint allowed-tools
Enter, inspect, or run the upgraded AirArc planning flow with built-in parallel review output. AirArc is architecture-only and must not write code.
enter|status|parallel-review
Read
Glob
Grep
Bash
Write
Edit

/airarc

Use the upgraded AirArc plugin for architecture-first planning and post-plan parallel review. AirArc only does architecture planning, task decomposition, and document updates; it does not implement code changes.

Steps

  1. Parse $ARGUMENTS; default to enter when empty.
  2. Run the matching mode from the current project root:
python "$HOME/plugins/airarc/scripts/airarc_mode.py" --mode <enter|status|parallel-review> --project .
  1. The runtime auto-bootstraps missing AirPlan/ files on first startup and does not overwrite existing project artifacts.
  2. If the request is a planning or architecture-change task, keep AirPlan/AGENTS.md, ADRs, C4 module docs, AirPlan/plan.md, and AirPlan/todo.md aligned with the new AirArc output.
  3. Do not write code, apply patches, or implement tasks directly from AirArc; hand confirmed execution work off to AirEng or other execution workflows.
  4. When planning needs UI or visual evidence, hand off screenshots or minimal GUI exploration to AirXDB before finalizing the plan.
  5. When parallel-review runs, record the emitted dependency edges, shared-write conflicts, serialization points, and execution-plan artifacts.