Problem
What needed to change
A team received a detailed RFP and needed more than a written response: stakeholders wanted a working prototype they could evaluate against the original requirements. Manually translating the document into architecture decisions, a backlog, and a build-ready repository would consume much of the evaluation window and make it difficult to trace the prototype back to the RFP.
Approach
Architecture + execution
- Uploaded the RFP PDF with a short seed brief in Navarch, preserving the original document privately while making its extracted requirements available to the connected planning agent.
- Used Navarch's private-repository fallback to create an isolated GitHub workspace when no customer repository was available, scoped to the project and its credentials.
- Had a plan session inspect the source material, identify assumptions and non-goals, and publish a repository-aware implementation plan with architecture, ordered work, acceptance criteria, risks, and verification steps.
- Converted the approved plan into focused build and verification tasks so fresh agent sessions could implement the highest-value workflow without losing the RFP context.
- Kept the prototype reviewable through normal GitHub pull requests, CI checks, task history, and human approval instead of treating generated code as an opaque one-off demo.
Results
Outcomes that held up
- Moved from a dense procurement document to a working prototype through one continuous, auditable workflow.
- Reduced interpretation and handoff time by grounding planning and implementation in the same RFP-derived context.
- Gave stakeholders a concrete prototype and traceable acceptance criteria for a faster, more useful evaluation conversation.
- Preserved a clean path from prototype to production: repository history, implementation decisions, tests, and open risks remained available after the demo.