admin/AirCoding
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
Files
f44b26bf825d1a5e29ac9e20cece3ca7a6b8c6c5
AirCoding/AirPlan/AGENTS.md
AirCoding b668b185e1 System detailed design: four-model cross-review complete 
Add system-detailed-design.md (2033 lines, 23 sections) derived from
frozen baselines and overview. Complete four-model cross-review:
- DeepSeek: baseline coverage audit (PASS, 9.6/10)
- MIMO 2.5 Pro: internal consistency (PASS, 9.4/10)
- GPT-5.5 Pro: baseline conflict detection (Requires repair)
- Opus 4.8: validation + root cause analysis (CONDITIONAL PASS, 9.1/10)

Key findings requiring resolution before freeze:
- P1-01: Worker exit code semantic conflict (baselineV1 vs overview)
- P1-02: PromptLayerLevel enum vs L0-L9 layer name mismatch
- P1-03: EventStore.project() error handling undefined
- P1-04: PromptLayerLoader interface incomplete for 10 layers

Coverage verified: 100% contracts, events, DB schema, state machines.
Architecture validated: no circular dependencies, proper separation.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-29 18:57:13 +08:00

4.5 KiB
Executable File
Raw Blame History

AGENTS.md

Workflow Root

  • This project uses AirPlan/ as the workflow root.
  • Keep planning, execution state, ADR, C4, validation, debug, and plugin runtime data under AirPlan/.
  • The repo-root AGENTS.md only bootstraps into this file.

AirArc Workflow

  1. Use AirPlan/AGENTS.md as the canonical project context entry point.
  2. Load and maintain:
    • AirPlan/docs/analysis/requirements.md
    • AirPlan/docs/architecture/solution-architecture.md
    • AirPlan/docs/architecture/system-overview-design.md
    • AirPlan/docs/architecture/gpt5概要设计审查.md
    • AirPlan/docs/architecture/mimo2.5概要设计审查.md
    • AirPlan/docs/architecture/Opus4.7概要设计审查.md
    • AirPlan/docs/architecture/DeepSeek概要设计审查.md
    • AirPlan/docs/architecture/概要设计修复回归审查.md
    • AirPlan/docs/architecture/概要设计修复回归审查-R2.md
    • AirPlan/docs/architecture/概要设计修复回归审查-R3.md
    • AirPlan/docs/architecture/system-detailed-design.md
    • AirPlan/docs/architecture/detailed-design-audit.md
    • AirPlan/docs/architecture/DeepSeek系统详细设计审查.md
    • AirPlan/docs/architecture/Mimo2.5pro系统详细设计审查.md
    • AirPlan/docs/architecture/gpt5.5pro系统详细设计审查.md
    • AirPlan/docs/architecture/opus4.8系统详细设计审查.md
    • AirPlan/docs/architecture/多模型系统详细设计交叉审查汇总.md
    • AirPlan/docs/architecture/baselineV1.md
    • AirPlan/docs/architecture/db-schema-v1.md
    • AirPlan/docs/architecture/event-registry-v1.md
    • AirPlan/docs/architecture/tool-registry-v1.md
    • AirPlan/docs/architecture/scheduler-state-machine-v1.md
    • AirPlan/docs/architecture/prompt-layering-v1.md
    • AirPlan/docs/architecture/provider-capability-matrix-v1.md
    • AirPlan/docs/architecture/error-taxonomy-v1.md
    • AirPlan/docs/architecture/artifact-naming-v1.md
    • AirPlan/docs/architecture/scope-escalation-v1.md
    • AirPlan/docs/architecture/security-model-v1.md
    • AirPlan/docs/architecture/capability-trust-v1.md
    • AirPlan/docs/architecture/cross-platform-matrix-v1.md
    • AirPlan/docs/architecture/branch-deepcode-cli/
    • AirPlan/docs/architecture/c4/module.md
    • AirPlan/docs/architecture/c4/code-view.md
    • AirPlan/docs/architecture/interface-contracts-v1.md
    • AirPlan/docs/architecture/runtime-semantics-v1.md
    • AirPlan/docs/architecture/多模型三视角审查联合评估.md
    • AirPlan/docs/architecture/adr/
    • AirPlan/docs/architecture/decisions-round-1.md
    • AirPlan/docs/architecture/decisions-round-2.md
    • AirPlan/docs/architecture/decisions-round-3.md
    • AirPlan/docs/architecture/main-agent-state-machine.md
  3. Produce or refine AirPlan/plan.md and AirPlan/todo.md.
  4. Keep plans optimized for lower-cost follow-up sessions, including scope, validation, file targets, and parallelization boundaries.
  5. AirArc is architecture-only: it may plan tasks and edit planning or architecture documents, but it must not write code or implement tasks directly.

AirEng Workflow

  1. Use /aireng as the sole scheduler for confirmed execution.
  2. Prefer AirPlan/state/airarc/reviews/execution-plan.json, then AirPlan/state/airarc/reviews/parallel-review.json, before falling back to local AirPlan/todo.md.
  3. Dispatch isolated /airdo subagents with bounded concurrency instead of defaulting to parent-thread coding.
  4. Monitor active workers on a 5-minute cadence, merge ready results, and continue later waves automatically when work remains.
  5. Keep AirPlan/todo.md, AirPlan/plan.md, AirPlan/AGENTS.md, ADR, and C4 docs synchronized during dispatch, monitoring, repair, and merge.
  6. AirEng owns global debug, XDB, repair, intervention, and document convergence, but it should only intervene directly for hard blockers and must return to scheduler mode immediately afterward.

AirDo Workflow

  1. Use /airdo for one narrow task slice from AirPlan/todo.md.
  2. Before editing, load:
    • AirPlan/AGENTS.md
    • AirPlan/docs/architecture/adr/
    • AirPlan/docs/architecture/c4/module.md
    • AirPlan/plan.md
    • AirPlan/todo.md
  3. Keep task-local progress resumable in AirPlan/state/airdo/.
  4. When AirEng owns orchestration, return shared document changes through documentUpdates.
  5. Route GUI work through AirXDB, debugging through AirDbg, network evidence through AirNDB, and static analysis through AirSDB when needed.
Reference in New Issue View Git Blame Copy Permalink