admin/AirCoding
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

chore: push all design docs, V2 plan specs, and current working state

Browse Source 
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>
This commit is contained in:
AirCoding
2026-06-12 17:12:29 +08:00
parent 8f55c962bb
commit ae44be31d5
364 changed files with 46779 additions and 2812 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
AirPlan/docs/spec/AirPlan-ParaV2/plugins/airarc/commands/airarc.md Executable file
View 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.