Skip to content

End-to-End: Claude + Conductor

This runbook is intentionally strict about unknowns. Anything not verified is marked with [RESEARCH REQUIRED].

  • Environment: Conductor workspace + Claude-based coding agent
  • Method: ACE (/auro.constitution -> /auro.charter -> /auro.plan -> /auro.tasks -> /auro.implement)
  • Outcome: shipped change + traceable artifacts
  1. Confirm repository and branch strategy:
  • Repo URL: <RESEARCH REQUIRED: canonical repo URL>
  • Default branch: <RESEARCH REQUIRED: protected branch policy>
  1. Confirm local prerequisites:
  • git --version
  • node --version
  • npm --version
  1. Confirm Auro CLI:
  • auro --version
  1. Confirm Conductor workspace setup details:
  • <RESEARCH REQUIRED: exact Conductor UI flow/versioned labels>
  1. Confirm Claude integration mode:
  • <RESEARCH REQUIRED: Claude model + tool permissions policy>
  1. Create/open workspace in Conductor.
  2. Ensure working directory is correct.
  3. Initialize Auro (if missing):
Terminal window
auro init <PROJECT_NAME>
  1. Validate .auro/ structure exists.

Expected artifacts:

  • .auro/constitution.md
  • .auro/templates/
  • .auro/scripts/

Run once per project:

/auro.constitution

Checklist:

  • principles are testable
  • constraints are explicit
  • no conflicting rules

If uncertain:

  • add [NEEDS CLARIFICATION: ...] instead of assumptions

Run:

/auro.charter "<feature request>"

Review for:

  • independent user stories (P1/P2/P3)
  • numbered requirements
  • measurable success criteria
  • edge cases

Stop condition:

  • no unresolved ambiguity markers

Run:

/auro.plan

Validate phase gates:

  1. Simplicity
  2. Anti-Abstraction
  3. Integration-First

Expected outputs:

  • plan.md
  • research.md
  • data-model.md
  • contracts/
  • quickstart.md

Run:

/auro.tasks

Validate:

  • every task maps to a user story
  • [P] markers only where safe
  • phases are dependency-correct

Run:

/auro.implement

Execution guardrails:

  • small commits per task cluster
  • run tests after each phase
  • stop and revise charter/plan if behavior drifts

Run project checks:

Terminal window
<RESEARCH REQUIRED: exact lint command>
<RESEARCH REQUIRED: exact test command>
<RESEARCH REQUIRED: exact build command>

Manual verification checklist:

  • happy path
  • one expected failure path
  • one boundary/edge case
  1. Open PR against main.
  2. Include artifact traceability:
  • charter section -> plan section -> task IDs -> commits
  1. Merge with CI green.
  2. Verify deployed URL:
  • <RESEARCH REQUIRED: environment URL>

If run gets stuck:

  1. Return to latest valid charter.
  2. Regenerate plan from charter.
  3. Regenerate tasks from plan.
  4. Continue implementation with smaller phase scope.
  1. Conductor version-specific UI flow
  2. Claude configuration and permissions
  3. Canonical CI commands for this repo
  4. Deployment verification URL/process