rfc-builder

To turn a PRD into an RFC, provide the problem description to initiate a discovery process that asks targeted questions, analyzes your codebase, and generates a structured Markdown RFC. The workflow drafts the complete document and allows section-by-section refinement.

Writing an RFC grounded in your codebase requires analyzing the repository to capture current architecture and constraints. The tool scans available code to ensure the generated Markdown RFC reflects actual technical limitations and structural reality.

Yes, you can generate a complete RFC draft first and then edit it section by section. The workflow produces a full Markdown document with templates and traceability, then supports iterative refinement so you can align individual sections independently.

You do not need a codebase available to start drafting an RFC. While codebase analysis grounds the document in reality, the workflow can construct a structured RFC solely from your PRD or problem description through guided discovery questions.

The RFC drafting process gathers missing context by asking targeted discovery questions based on your initial problem description. This ensures the generated Markdown document captures necessary architectural details and stakeholder requirements before producing the draft.

The final RFC document uses Markdown format for stakeholder review. This structured output includes standard RFC sections, templates, and traceability to ensure stakeholders can quickly understand and approve the proposed architecture.