spec-driven-brainstorm

Spec-driven brainstorming converts conversational intent into an issue-organized spec.md containing boundary-aware, absolute acceptance criteria, ensuring vague ideation becomes confirmable product facts.

Maintain consistency by detecting contradictions after each update and cascading revisions within the same issue, ensuring upstream changes automatically propagate through the spec.

Grow the spec.md progressively through ordered subsections—Definition, Problem Space, Brainstorming, Solution, Examples, and Implementation—using batch questions to guide clarification and maintain disclosure order.

Yes, atomic archiving saves prior brainstorming verbatim upon variant commit, forcing selected solutions to be committed while preserving the entire ideation history for auditability.

Specifications contain hedging when strict as-is style constraints are absent; applying absolute, non-hedged writing rules rewrites inputs into confirmable facts without Q&A or transitional narratives.

Spec-driven brainstorming operates with zero external dependencies, relying solely on conversational prompts to resolve ambiguity via batch questions and maintain spec invariants throughout multi-round ideation.