proposal-readiness-check

To check proposal readiness for spec, evaluate the document against a five-criteria checklist covering intent clarity, story specificity, scope boundaries, change size, and open questions. This validation surfaces gaps and prompts for missing information before spec review.

Proposal readiness validation is a quality-check process during the brainstorm to spec transition. It applies five readiness criteria to proposal.md to ensure inputs are complete, preventing escalations and low-quality specs during the spec phase.

To identify open questions and scope gaps before writing a spec, run a readability check that flags missing scope boundaries and unresolved queries. This surfaces follow-up questions to keep brainstorm and spec phases aligned.

A proposal should meet five criteria before moving to the spec phase: intent clarity, story specificity, scope boundaries, change size, and open questions. Meeting these ensures the proposal.md has sufficient detail for spec generation.

No, the proposal readiness check requires no dependencies or components. It operates directly on proposal.md to validate readiness for spec by enforcing the five criteria and surfacing gaps for user clarification.

You should avoid using a proposal readiness checklist if your proposal.md is still in early brainstorming phases lacking basic intent. The check is designed for the brainstorm to spec transition to validate completeness, not to generate initial requirements.