[v1.1] Iterative document generation — review gate between each spec file

[FredAntB]

Source

HN beta feedback from jfim during v1.0-beta launch.

Problem

The skill currently one-shots all three spec files after the
interview completes. The user has no review gate between
requirements.md and design.md — a bad requirements pass gets
built on immediately.

Proposed change

After generating requirements.md, pause and ask:
"Here's your requirements.md — does this look right, or should
we adjust anything before I generate the design?"

Only proceed to design.md after explicit user confirmation.
Same gate between design.md and tasks.md.

Impact

• Catches bad first-pass requirements before they propagate
• Gives users natural checkpoints to course-correct
• Slightly more friction but significantly better output quality

Labels

v1.1, beta-friction