Extract engineering boundaries from a draft
The requirement assistant accepts natural language and project context, then structures goals, constraints, and verifiable criteria without inventing product decisions.
REQUIREMENTS → ACCEPTANCE
Define what done means before agents start writing.
PiGO places requirement refinement before execution. Goals, context, and acceptance criteria travel with the Story and Run through planning, development, review, and the final release record.
Acceptance criteria survive the entire run
The Planner uses them to scope work, Developers use them to assess implementation, gates provide execution evidence, and the Reviewer judges against the same standard.
Agile objects stay connected to agent execution
Project → Sprint → Story → Run → Release records how intent became code, how many repair rounds happened, who approved it, and when it moved to release.
IMPLEMENTED, NOT IMPLIED
Traceable requirement objects
- Projects and sprints
- Story goals and acceptance criteria
- Requirement Assistant history
- Run input snapshots
- Release summaries and retrospectives