PM (Product Manager)
Defines what gets built and why, gates spec sign-off, and protects user value against scope drift.
New chapter weekly · Follow The Agentic Shift on LinkedIn
Governance for AI-assisted development.
A three-role Triad and a six-stage lifecycle that produce specs the agent cannot bypass at build time.
Why ungoverned AI development fails.
- Context drift. The agent forgets what was decided two prompts ago, and rebuilds the same wrong assumptions on every fresh session.
- No governance. Specs and plans get drafted, approved, and then quietly bypassed at build time when the agent reaches for a shortcut.
- Vibe coding. Prompts replace specifications. What ships is whatever the model felt like producing on that run, not what the team agreed to.
Triad governance, six-stage lifecycle.
Architect
Defines how the system is built, locks the technical baseline, and gates plan and tasks sign-off against feasibility.
Team-Lead
Defines when work happens and who picks it up, sequences parallel waves, and gates tasks sign-off against capacity.
ADLC
- Discover
/aod.discoverCapture an idea, score it with ICE, decide whether it earns a slot in the backlog. - Define
/aod.defineWrite the PRD with Triad sign-offs — what gets built, why, and what success looks like. - Plan
/aod.planTranslate the PRD into spec, project plan, and tasks with PM, Architect, and Team-Lead sign-offs. - Build
/aod.buildExecute the tasks in parallel waves with Architect checkpoints at every critical phase. - Deliver
/aod.deliverVerify the Definition of Done, run the retrospective, and close the feature. - Document
/aod.documentReview code for simplification, refresh docstrings, update CHANGELOG and API docs.
AOD treats the spec as the contract the agent works against, not a suggestion it can route around. Every artifact — PRD, spec, plan, tasks — carries explicit Triad sign-offs at a build-time gate. The agent runs the same slash commands every session, against the same locked artifacts, and produces the same kind of output across runs and across humans.
What ships in AOD-Kit.
Triad Governance
Three named roles — PM, Architect, Team-Lead — with sign-off gates at every stage boundary. The artifact never ships without all three approvals.
Product Discovery
Capture ideas, score them with ICE, and validate against vision and OKRs before they reach the PRD stage. Skips nothing, scores everything.
Stack Packs
Switchable conventions for the agent — currently five packs covering Next.js, FastAPI + React, SwiftUI, and a knowledge-system stack.
Security Scanning
Claude-led SAST and SCA review on every build, blocking on Critical and High findings before merge.
Kickstart
A POC kickstart skill that turns a project idea into a sequenced consumer guide with six to ten seed features.
Thinking Lenses
Fourteen structured methodologies — 5 Whys, Pre-Mortem, First Principles, Systems Thinking — routed by context for systematic analysis.
Where the work stands.
Built with AOD. See how AOD built Tachi →
Where to start, by role.
Solo Developer
30 minutesRun the Triad on your next feature without process overhead — branch, build, ship.
Team Lead
45 minutesEvaluate three-role governance for a team-scale agent-assisted SDLC.
Evaluator
10-min preview · 4-hour readRead the methodology before recommending or adopting it.
These cards triage. Deeper role-tailored journeys are a v1.1 backlog item.
Need help adopting AOD?
I want to help you use it. If you are running an agent-assisted SDLC and the methodology is not landing — context drift on long features, sign-offs getting bypassed, governance feeling theatrical — book a 30-minute call. We will walk one feature through the Triad together, end to end. Personal coaching, not a sales pitch.