From a conversation to shipped code, one pipeline
I am building a small ecosystem of skills, frameworks and tools to ship faster without shipping sloppier. Everything goes through GitHub, because that is where the code ships: notes, briefs, specs, issues and pull requests live next to it.
CaptureMeetings and raw ideas land in one inbox, then get routed to the right project after I approve the plan. No silent move.
- Call recording → dated Markdown note in git
SynthesizeTurns a transcript into a structured note: decisions and actions for a meeting, jobs and frictions for user research, scenario by scenario for a prototype test.
- Transcript → synthesis note
GrillAn interview that stress-tests the idea, one decision per question, before anything gets written. The agent finds the facts, I make the calls.
- Rough idea → list of settled decisions
PRDThe alignment document: the what and the why, shared by tech, design and business. The only artefact meant to outlive the feature.
- Synthesis + decisions → brief
PrototypeSomething clickable to align on before the spec hardens. It has its own lab.
- Brief → clickable prototype
Gherkin specThe feature spec, with given / when / then scenarios. It is the contract automated QA reads later.
- Brief → scenarios
ImplementBuilds one vertical slice at a time with tests at the agreed seams, then reviews the diff on two axes: does it do what the plan asked, and does it respect the repo's own architecture rules.
- Scenarios → PR with a preview deploy
Automated QAReads the Gherkin scenarios and runs them: classic end-to-end tests, Playwright MCP, and briefs that Claude executes in the browser extension.
- Scenarios → test run
Manual QAI browse the preview and share what I see; the issues write themselves, triaged with labels.
- Screen capture → GitHub issue
Auto-fixAn agent picks up triaged issues and opens the fix as a pull request. Not tested yet.
- Issue → fix PR
DocumentationTurns a shipped feature into product documentation and publishes it to GitBook.
- Shipped feature → GitBook page
Release notesWrites the release note from the merged work, in the house format.
- Merged PRs → release note
AnalyticsClose the loop: read what shipped features actually do in production, feed it back into discovery.
- Production usage → next discovery
Why GitHub is the rail
A synthesis that lives in one tool, a spec in another and the tickets in a third drift apart within a week. When every artefact is a file or an issue in the same place as the code, an agent can read the whole chain, and so can I.
Credits
The interview, the build loop and the two-axis review come from Matt Pocock's skills, used as they are. Two skills started as internal tooling on an Agicap engagement.
Log
- 18 September 2026 — First version. Prototyping and the Gherkin spec skill are still in progress; analytics is next.