Agentic Engineering Pipeline
The ticket-to-merged-PR pipeline that builds this very portfolio: eight agents, board-driven, with guardrails like batch-approval gates and human-only priority calls.
This portfolio is built by an agentic engineering pipeline, not by hand-editing files in isolation. A ticket becomes a merged PR by moving through eight tool-mediated stages, each with its own agent and its own guardrails.
How it flows
Design decisions
A batch-approval gate before any tickets exist
roadmap drafts an entire batch of tickets from a discussed plan, then shows the whole batch for review before creating a single one. A single bad ticket is a five-minute fix; a batch of a dozen bad tickets silently seeded into the board is a much bigger cleanup — so the gate sits before creation, not after.
planning-agent talks, and never touches Priority
planning-agent runs as a conversational session, not a cron job, and it's deliberately barred from ever writing to the board's Priority field. Sequencing what matters most is a judgment call about the business, not something an agent should infer from ticket text — it stays a human decision, every time.
comment-resolver-agent stops after two attempts
When a PR is rejected in code review or QA, comment-resolver-agent gets two tries to fix the specific findings and push again. If it still isn't right after that, it hands off to a human instead of looping — an agent stuck in a fix-reject cycle burns time and CI minutes without getting closer to done.