Spec to Ship: From Product Spec to Implemented Feature with Agents
NEO wired a multi-agent flow: a written spec becomes plans, tasks, and code changes. Planner, implementer, and reviewer roles stay coordinated so features move faster but still have guardrails.
Problem Statement
We asked NEO to connect product specs to engineering. Specialized agents should break work down, implement in-repo, and review diffs, while every change stays traceable to the original requirements.
Solution Overview
- Spec parse: Pull out requirements, acceptance criteria, and risks.
- Plan: Planner agent outputs milestones and file-level tasks.
- Implement & review: Coder and reviewer agents with human approval where you want it.
Workflow / Pipeline
| Step | Description |
|---|---|
| 1. Intake | Spec markdown or ticket body ingested |
| 2. Decompose | Planner creates ordered tasks with dependencies |
| 3. Build | Implementer applies patches; tests run in CI sandbox |
| 4. Verify | Reviewer checks against acceptance criteria; human approves merge |
Repository & Artifacts
Generated Artifacts:
- Orchestration config for agent roles and tools
- Trace logs mapping commits back to spec sections