create-dev-spec — From Rough Requirement to Approved Specification

Core Principle

A specification written alone is a guess with headings. This workflow makes the spec a co-authored document: you bring structure, the questions the user has not asked themselves yet, and concrete proposals; the user brings intent, domain knowledge, and the final say. Nothing that shapes the spec is decided silently — every gap becomes a question, every question gets your best proposal plus room for the user's own answer, and every answer is recorded as a decision the spec can cite.

The output is two files: