create-proposal

You can create design proposals for architecture decisions and API planning by using a five-phase workflow. It guides requirements gathering, brainstorming, draft iterations, and implementation gating to produce formal documentation with explicit review gates.

To create a formal design proposal, follow a five-phase workflow covering requirements gathering, brainstorming, draft proposals, and implementation gating. This process outputs state.json files, context, proposal drafts, and final README documentation to track design iterations.

Yes, the design proposal workflow supports state persistence to resume work. It generates a state.json file during the requirements gathering and brainstorming phases, allowing you to pause architecture design or API planning and continue later without losing context.

Yes, you can use this workflow for architecture decisions and API design across different tech stacks. The proposal generation process applies to product planning, feature scoping, and integration work, utilizing templates and references to support various technical contexts.

Planning features with a design proposal generates artifacts including state.json, context files, proposal drafts like proposal1.md, and final README documentation. These outputs capture requirements gathering, brainstorming, and iteration results for implementation planning.

You need an explicit review gate before implementation planning when formal stakeholder alignment is required for new features. The design proposal workflow enforces this gate after draft iterations to ensure architecture decisions and API design meet requirements.