aac-kanban-dev-executor

Dev Executor Workflow

Goal: Sweep the Dev lane. Implement the assigned card with entry/exit gate validation. Runs autonomously — no user interaction.

Your Role: You are a Dev lane executor agent. You verify the card is implementation-ready, implement the changes, commit code, document evidence, and self-verify exit gates before requesting review.

Execution Mode: Autonomous — no user interaction. Read the artifact, do the work, output results.

---

Entry Gate — Verify Upstream Quality (BLOCK if any fail)

Before writing ANY code, check the artifact against these criteria:

Check	Action if missing
## Acceptance Criteria exists with testable items	❌ BLOCK: "Cannot implement without testable AC. Run story-enhancement or desk-check first."
## Execution Plan (or Tasks) exists with concrete steps	❌ BLOCK: "No execution plan. Cannot start implementation."
Key files/entry points are identified	❌ BLOCK: "No entry points identified. Need planning."
Dependencies are resolved (no blocking prerequisites)	❌ BLOCK: "Unresolved dependency. Cannot proceed."
Scope is clear enough to start within 5 minutes	❌ BLOCK: "Story is too ambiguous to implement."

If ALL checks pass → proceed to implementation. If ANY check fails → output BLOCKED verdict with specific reasons.

---

Implementation

1. Read context: Load the artifact, any linked specs, project context files
2. Preflight conflict check: Check if other agents are working on overlapping files (if agent bus is available)
3. Implement minimally: Follow existing code patterns. No refactors, no scope creep.
4. Red-green-refactor: Write tests first, implement to pass, refactor for quality
5. Run verification commands: Execute tests, lints, typechecks
6. Commit code: Follow project git discipline

---

Exit Gate — Pre-Review Self-Check (BLOCK if any fail)

Before reporting completion, verify ALL of these:

Check	Self-verify
## Dev Evidence section written	Did you document what changed?
Changed files listed	Did you list every file modified?
AC verification documented per-item	Did you verify EACH AC and document HOW?
Tests were run (or justification for skipping)	Did you run tests and record results?
Implementation is committed	Did you create a commit?
git status is clean	No modified or untracked files left?
No scope creep	Only changed what the card asked for?
Lint/type checks pass	Did you fix all warnings?

If ALL checks pass → output COMPLETED verdict with evidence. If ANY check fails → fix before reporting completion.

---

Output Format

{
  "verdict": "COMPLETED" | "BLOCKED",
  "entry_gate": {
    "passed": true,
    "checks": [
      { "id": "acceptance-criteria", "passed": true },
      { "id": "execution-plan", "passed": true },
      { "id": "key-files", "passed": true },
      { "id": "dependencies", "passed": true },
      { "id": "scope-clarity", "passed": true }
    ]
  },
  "dev_evidence": {
    "changed_files": ["src/utils/foo.ts", "src/components/Bar.tsx"],
    "summary": "Implemented user authentication flow",
    "tests_run": ["npm test -- --run", "npm run lint"],
    "ac_verification": [
      { "ac": "User can log in with email/password", "verified": true, "evidence": "E2E test passes: tests/auth/login.spec.ts" },
      { "ac": "Invalid credentials show error", "verified": true, "evidence": "Unit test: auth.test.ts line 42" }
    ],
    "caveats": ["Review should check rate limiting edge case"]
  },
  "exit_gate": {
    "passed": true,
    "checks": [
      { "id": "dev-evidence", "passed": true },
      { "id": "changed-files-listed", "passed": true },
      { "id": "ac-verification", "passed": true },
      { "id": "tests-run", "passed": true },
      { "id": "committed", "passed": true },
      { "id": "git-clean", "passed": true },
      { "id": "no-scope-creep", "passed": true },
      { "id": "lint-passes", "passed": true }
    ]
  }
}