Files

T

CI / build (push) Has been cancelled

Details

Add code_review phase with approval gate, reviewer≠implementer enforcement, and structured CODE_REVIEW.md

- Insert code_review phase between implement and bug_find
- Approval gate: code_review:awaiting_approval → code_review:approved
- Read-only phase — no edits, no fixes, no returning to implement
- Reviewer≠implementer: .state.implementer tracking + --claim enforcement
- Structured CODE_REVIEW.md: spec compliance, design conformance, quality
  scorecard, items found (severity/category/location/resolution), test coverage
- Updated status.py (10 data structures), dashboard (4 files), prompts (3 files),
  agent routing, tests (6 new test classes, 19 new tests)

2026-06-16 09:00:22 -04:00

2.9 KiB

Raw Permalink Blame History

.agent.md

Autopilot

Autopilot: Enabled

Note: For global framework settings (VRAM, model, system requirements), see ~/.automaton/config.md.

Routing

IF task type = research → load prompts/research.md + .rules.md IF task type = design → load prompts/design.md + SPEC.md IF task type = test_design → load prompts/test_design.md + SPEC.md + DESIGN.md IF task type = implement → load prompts/implement.md + SPEC.md + DESIGN.md + TEST_PLAN.md + CONTRACT.md IF task type = code_review → load prompts/code_review.md + SPEC.md + DESIGN.md + IMPLEMENTATION.md IF task type = bug_find → load prompts/bug_finder.md + SPEC.md + code IF task type = adversarial_bug_find → load prompts/adversarial_bug_find.md + SPEC.md + code IF task type = referee → load prompts/referee.md + SPEC.md + BUG_REPORT.md + ADVERSARIAL_BUG_REPORT.md + DOC_REVIEW.md IF task type = doc_review → load prompts/doc_review.md + DESIGN.md IF task type = decompose → load prompts/decompose.md + SPEC.md IF task type = orchestrate → load prompts/orchestrate.md + project structure IF task type = compaction → load prompts/compaction.md

Always start by reading this file to determine mode.

State Enforcement (v2.0)

All phase transitions must go through status.py:

Create tasks: python ~/.automaton/scripts/status.py --create-task {name} --project {project}
Transition phases: python ~/.automaton/scripts/status.py --transition {phase} --task {name} --project {project}
Approve phases: python ~/.automaton/scripts/status.py --approve --task {name} --project {project}
Validate folders: python ~/.automaton/scripts/status.py --validate-folder --task {name} --project {project}
Audit all tasks: python ~/.automaton/scripts/status.py --audit --project {project}
Upgrade pre-v2.0 tasks: python ~/.automaton/scripts/status.py --upgrade --project {project}

Important: Always pass --project {project} to ensure correct scoping. Without it, status.py resolves the project from the current working directory, which can target the wrong project when multiple projects exist on the same machine.

Agent Configuration (Optional — Multi-Agent Mode)

To enable multi-agent mode, add the following section:

## Agent Configuration
Mode: multi-agent
Agents:
  - id: researcher
    phases: [research, decomposition, design, test_design]
  - id: implementer
    phases: [implement]
  - id: code-reviewer
    phases: [code_review]
    role: reviewer
  - id: bug-hunter
    phases: [bug_find, adversarial_bug_find]
  - id: referee
    phases: [referee]
  - id: orchestrator
    phases: [new, complete, human_intervention]
    role: coordinator
Lock timeout: 30m

When Mode: multi-agent is present, agents can claim tasks (--claim), release them (--release), and discover work (--next-available). When absent (default), all multi-agent commands are no-ops.