create-rfd

Document technical decisions by creating a Request for Discussion (RFD) that structures problem statements, evaluates architectural options, and preserves design rationale. RFDs guide proposals through defined lifecycle states like Ideation, Discussion, Published, and Committed for clear team tracking.

Building consensus before implementation is best achieved through an RFD process that structures technical exploration and captures considerations. By managing RFD states from Ideation to Committed, teams collaboratively evaluate alternatives and formalize agreement before development begins.

Structure a technical proposal using predefined RFD sections for problem statements, options, and considerations. This format systematically documents the evaluation of alternatives, such as comparing microservices to a monolith, ensuring the chosen architectural path and rationale are preserved for future reference.

You need a formal technical decision making process when proposing new architectural approaches that require structured exploration and team alignment. Using RFDs ensures design rationale and consensus building steps are documented through a managed lifecycle, preventing future context loss.

Yes, you can use an RFD to track a caching strategy proposal through clear lifecycle transition rules. The process manages RFD states from initial Ideation and Discussion to Published and Committed, maintaining an index for ongoing discovery and tracking of the technical decision.

Managing RFDs and their discovery index requires no external dependencies or tools. The process operates independently using scripts and references to handle file locations, lifecycle state transitions, and the structured documentation needed for technical proposals.