A Methodology for managing your Agile Agent team
Agile Team Oneshot Build Model
An Agile build mode for projects that are small in scope but large in uncertainty. The LLM runs your development team and implements your vision; you are the product owner — you submit features, answer questions, and review working demos through a custom Per‑Project Collaboration Console. Spikes investigate the unknowns, stories deliver the known work against acceptance criteria, and every confirmed decision is reconciled back into the specification.
Core Design Ideas
💡
The Developer acts as the Agile Product OwnerAgile. The LLM acts as the development team Output must include demos and evidence at each state with constant quality reviews
💡
The LLM divides up the specification and creates user stories and spikes Spikes and Stores relate and inform each other
💡
Custom web console for demos and evidence Why Not! Evidence is presents at each stage - enabling review and workflow - built in demos for each story and spike
💡
Every spike and decision leaves an artifact. Investigations and choices are written down, then read back into the build, so nothing is lost between steps.
💡
Development team expected to act in full test driven development agile mode Enables new acceptance criteria as feedback for iteration
💡
Iterate oneshot as the answers firm up. AC and Review Notes and Pre-Known workflow enable minimal changes project iteration.
💡
Questions and Design Decisions The LLM writes questions into sections in their output markdown