PHEN
← All case studies

// Case Study

Agentic Delivery Pipeline

A lean crew at BD Performing Arts was buried under a runaway stakeholder backlog. I built them an agentic pipeline that absorbs the PM, QA, and Technical Writer work. The humans pick what gets shipped. Quick tickets close 4× faster, every cycle ships with its own docs, and the system gets sharper every time.

Agentic AIProject Ops

// The challenge

Lean
crew.

Runaway
backlog.

BD Performing Arts runs with a lean crew: no PM, no QA team, no technical writer, and a stakeholder list that never stops growing. Staff, parents, board members, and performers all file requests through one internal tool. Each ask carries a real timeline. Tickets piled up faster than the crew could touch them, and the backlog only ever grew.

So I built them an agentic pipeline that absorbs the three missing roles. The agent carries the manual work. The humans carry the judgment.

// The pipeline

A request lands and the agent carries it from triage to docs. The humans sign off where it counts. Every cycle ships its own user-facing write-up and feeds the agent's memory for the next ask.

01STAKEHOLDERS Staff, parents, board members, and performers all file through one internal door. Every ask becomes a ticket. 02TASKBOARD A custom Laravel board with its own REST API. Tickets, projects, and sprints sit behind endpoints the agent can call. 03TRIAGE The agent reads every new ticket the moment it lands. Fingerprint dedup catches duplicates; tags route to the right project. 04SCOPE The agent sizes the effort, drafts the scope, and writes the user-facing summary the submitter will see on the ticket. 05APPROVAL The user who filed the ticket reviews and approves the scope. Edits lock so nobody rescopes mid-conversation. REVOKE 06SPRINT Approved tickets rank by effort × human override. The crew fills the queue top-down; the agent picks up the rest. 07BUILD OpenClaw writes the code, opens a branch, and ships a pull request. Every change is traceable to its ticket. 08TEST + VALIDATE Playwright walks the real user flows. An AI reviewer reads every diff and blocks lazy commits before merge. FAIL 09DONE The PR merges. A completion summary lands on the ticket with what changed, why, and where to find it. 10DOCS DELIVERED The system writes user-facing docs and emails the link to the submitter. The agent reads the same docs as memory next time.
From stakeholder ask to delivered docs. Solid arrows are the normal flow. Dashed loops are the two ways back: the user revokes the ticket, or tests fail and the ticket bounces to the dev queue. Every completed cycle leaves docs and a summary behind for the agent to read on the next ask.

/ Roles, offloaded

Three jobs the agent quietly absorbed.

// The PM

Triage, size, scope.

Before: someone had to read every ask, size it, and write the scope back to the requester. After a few weeks the queue was the project manager.

After: OpenClaw drafts the triage and the scope in seconds. The human reads it in thirty and signs off.

// The QA

Test, validate, sign off.

Before: smoke tests in someone's notebook, regression sweeps after every release, browser checks by hand.

After: Playwright walks the real flows on every PR. An AI reviewer reads every diff and reruns the suite until green.

// The Tech Writer

Docs that ship with the feature.

Before: docs were a permanent TODO. By the time anyone wrote them, the feature had already changed.

After: each shipped ticket writes its own user-facing doc; the submitter gets the link, the agent reads the same docs as memory next time.

THE OUTCOMES

Quick tickets close 4× faster. The crew got their evenings back. The system gets sharper every cycle.

4×

Quick tickets out

What used to chew on for weeks closes in days. Triage and sizing run while the crew sleeps.

PM hours,
offloaded.

Triage to handoff

Sizing, scoping, and the user-facing approval message all draft themselves. The humans sign off where it counts.

Tests + reviews,
on every PR.

QA, fully automated

Playwright walks the real user flows on every PR. An AI reviewer reads every diff, catches lazy commits and security smells, and holds the line on main.

Docs that
feed back in.

Self-improving loop

Every shipped ticket writes its own docs and a completion summary. The submitter gets the link in their inbox. The agent reads its own history on the next similar ask, so the next scope is sharper than the last.

/ The payoff

A lean crew that ships like a full team, with the paper trail to prove it.

Stakeholder questions used to put the crew on its back foot. Now they open the board, point at the ranked list, and walk the stakeholder through what shipped, what is queued, and where the humans overrode the agent.

When a ticket lands in Done, the docs land in the submitter's inbox and the completion summary lands on the ticket. The next similar ask gets a sharper scope because the agent reads its own history. Nothing falls off the board.

Same pipeline runs on phenpedron.com. Same taskboard, same agent, same handoff loop. I built it for myself first, tuned a copy for BD Performing Arts, and I am ready to do the same for the next team that wants this kind of leverage.

Hire me, or hire the playbook →