Initial release: airarc
This commit is contained in:
24
commands/airarc.md
Normal file
24
commands/airarc.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
description: Enter, inspect, or run the upgraded AirArc planning flow with built-in parallel review output. AirArc is architecture-only and must not write code.
|
||||
argument-hint: [enter|status|parallel-review]
|
||||
allowed-tools: [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:
|
||||
|
||||
```bash
|
||||
python "$HOME/plugins/airarc/scripts/airarc_mode.py" --mode <enter|status|parallel-review> --project .
|
||||
```
|
||||
|
||||
3. The runtime auto-bootstraps missing `AirPlan/` files on first startup and does not overwrite existing project artifacts.
|
||||
4. 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.
|
||||
5. Do not write code, apply patches, or implement tasks directly from AirArc; hand confirmed execution work off to AirEng or other execution workflows.
|
||||
6. When planning needs UI or visual evidence, hand off screenshots or minimal GUI exploration to AirXDB before finalizing the plan.
|
||||
7. When `parallel-review` runs, record the emitted dependency edges, shared-write conflicts, serialization points, and execution-plan artifacts.
|
||||
Reference in New Issue
Block a user