think

Turn a vague product idea into a buildable specification by working backwards from an imagined shipped announcement, capturing claims, and interrogating honesty conditions until the frame converges. The method constructs an Announcement Frame through iterative claim capture and convergence gating.

The working-backwards approach for product requirements builds a spec from a hypothetical feature announcement, pressure-testing claims and parking unknowns explicitly. It ensures product requirements are evidence-backed and validated before planning or implementation begins.

Pressure-test incomplete feature requirements by applying claim capture and honesty interrogation within a deterministic move-driven workflow. You confirm or reject proposed claims and park unknowns until convergence gating validates overall spec readiness.

No, you cannot export a product specification before passing convergence gating. The workflow requires the converge move to pass a readiness gate, ensuring all honesty conditions are confirmed and open vagueness is resolved before exporting buildable artifacts.

No, the specification workflow does not require a fixed prompt sequence. It uses strict move-driven CLI execution with verbs like new, capture, interrogate, confirm, reject, park, converge, and export, allowing flexible navigation through the claim validation process.

Avoid using convergence gating for feature framing when your requirements are already fully validated and implementation-ready. The process is specifically designed for incomplete or uncertain product and engineering ideation that must be pressure-tested before planning.