Write intro documentation explaining what ATS Project Runner is and why it exists

[mikkel]

ATS Task #483

Create a doc/INTRO.md file that explains the what and why of ATS Project Runner. This should be a compelling introduction document that covers:

1. What it is — An automated PR factory. You give it a task description on an ATS channel, and it creates a branch, runs Claude Code to implement the changes (with iterative refinement), commits, pushes, and opens a PR. Zero human involvement from task to PR.

2. Why it exists — The bottleneck in AI-assisted development isn't the AI writing code — it's the human orchestrating it. Copy-pasting task descriptions into Claude, managing branches, reviewing iteration output, opening PRs. ATS Project Runner eliminates that entire loop. You describe what you want, it ships a PR.

3. How it works (brief, not a full technical spec):

   • Watches an ATS channel for new tasks
   • Creates a working branch from main
   • Feeds the task description to Claude Code as a prompt
   • Runs iteratively (Claude signals TASK_COMPLETE when done)
   • Commits, pushes, opens a PR linking back to the original task
   • Original task stays pending for human review of the PR

4. The design philosophy — Why it copies the task instead of claiming it. Why iterative mode. Why it's a thin orchestrator that delegates all intelligence to Claude Code.

5. Where it fits — Part of the DiffLab ATS ecosystem. Works alongside ada-dispatch, song-creator, review-responder, and other ATS channel workers.

Write this in a clear, direct style. No fluff, no marketing speak. Technical audience. Think of it as the doc you'd want to read before deciding whether to set up your own project runner.

Use 4 iterations to refine the document — first draft, then improve clarity, then tighten prose, then final polish.

---

Mode: iterative | Iterations: 2 | Run: 1
Generated by ATS Project Runner v3.0.0

[mikkel]

@/ml2/nanobot/.pr-review-state/review-body.tmp