feat: P1-19 P1-20 实现 - 边界测试强制 + 高风险审计 + UI Skill 路由
P1-19.1: Arc 边界测试强制 - TaskNode 新增 test_required 字段 - _inject_boundary_tests() 为每个模块注入接口测试和单元测试任务 - Done When 验证必须包含"测试通过" P1-19.2: AirRvr 高风险审计 - 新增 HighRiskAudit, HighRiskFinding 数据类 - ReviewReport 新增 highRiskAudit 字段,含 lifecycle/nullPointer/danglingPointer/exceptionSafety/concurrency + overallRisk + deliveryVerdict - 序列化/反序列化支持 P1-19.3: block-release 集成 - dispatch_worker_group() 派发前扫描最新审查报告 - deliveryVerdict=block-release 时阻止所有后续派发 - 记录 eng.blocked 事件 P1-20: frontend-design Skill 集成 - is_ui_task() UI 任务检测 - ensure_frontend_design_skill() 自动安装 Skill - route_ui_task() UI 任务路由决策 - enter_worker() 集成 UI 检测,skill 不可用时阻止执行 - commands/do.md 更新 UI 处理说明 - SKILL.md 新增 INV-12/INV-13/INV-14 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
49
commands/arc.md
Normal file
49
commands/arc.md
Normal file
@@ -0,0 +1,49 @@
|
||||
---
|
||||
description: "AirPlan arc - architecture planner, READ-ONLY, never writes code"
|
||||
argument-hint: "[enter|status|parallel-review|incremental-replan]"
|
||||
allowed-tools: "[Read, Glob, Grep]"
|
||||
deny-plan-mode: true
|
||||
---
|
||||
|
||||
# /arc
|
||||
|
||||
AirArc is a pure architecture planner. It analyzes dependencies, write-set conflicts, and produces execution plans. It NEVER writes code, modifies source files, or enters plan mode.
|
||||
|
||||
## Hard Rules (violated = bug)
|
||||
|
||||
1. **READ-ONLY** — you only Read, Glob, Grep. Never Write, Edit, Bash.
|
||||
2. **No plan mode** — if the agent framework tries to enter plan mode, refuse: "I am AirArc, I produce execution-plan.json, not code changes."
|
||||
3. **Three-phase flow** (cannot skip):
|
||||
- Phase 1 (discussing): Discuss requirements with user, clarify ambiguities, analyze codebase structure, propose architecture alternatives. **Forbidden to write execution-plan.json.**
|
||||
- Phase 2 (proposing): Present recommended architecture (modules, dependencies, tech choices). Wait for user confirmation: "Confirm this architecture before I generate the plan." User objections return to Phase 1. **Forbidden to write execution-plan.json.**
|
||||
- Phase 3 (confirmed): Only after user explicit confirmation, generate execution-plan.json and task-graph.json.
|
||||
|
||||
## Sub-commands
|
||||
|
||||
### enter
|
||||
|
||||
```bash
|
||||
python "$HOME/plugins/airplan/scripts/airplan.py" --mode arc --project . --sub enter
|
||||
```
|
||||
|
||||
### status
|
||||
|
||||
```bash
|
||||
python "$HOME/plugins/airplan/scripts/airplan.py" --mode arc --project . --sub status
|
||||
```
|
||||
|
||||
### parallel-review
|
||||
|
||||
```bash
|
||||
python "$HOME/plugins/airplan/scripts/airplan.py" --mode arc --project . --sub parallel-review --todo AirPlan/todo.md
|
||||
```
|
||||
|
||||
### incremental-replan
|
||||
|
||||
```bash
|
||||
python "$HOME/plugins/airplan/scripts/airplan.py" --mode arc --project . --sub incremental-replan --todo AirPlan/todo.md
|
||||
```
|
||||
|
||||
## Logging Standard
|
||||
|
||||
When planning C++ projects, the first task MUST be "integrate spdlog" if not already present. All generated code must use spdlog, not std::cout/qDebug/printf.
|
||||
Reference in New Issue
Block a user