novahiz-assess-intakelisted

# novahiz-assess-intake **Step 1 of 5** in the assessment roadmap. No file changes here. The deliverable is a clean capture of the idea. Previous step: none, this is the entry. Next step: `novahiz-assess-research`. ## Entry The user brings an idea, a feature request, or a product concept. It may be vague, partial, or self-contradictory. Capture it cleanly. Judging comes later. ## What to capture ### 1. Core statement One sentence: what it does, for whom, and why it matters. ### 2. Problem statement What pain, gap, or opportunity does it address? What happens if nothing is built? ### 3. Target audience Who benefits? "Developers" is too broad. "React developers who deploy to Vercel" is actionable. ### 4. Initial scope boundaries Clearly in, clearly out, and still uncertain. ### 5. Constraints known so far Timeline, budget, and people. Platform, stack, and integrations. Compliance and market timing. ### 6. Success signals Concrete, measurable outcomes that would prove the idea works. ## Capture method Use the harness `question` tool. One batch, ranked by impact on the later spec: ``` question({ questions: [ { header: "<what's missing>", question: "<why it matters for the assessment>", options: [ { label: "<recommended>", description: "<consequence>" }, { label: "<option>", description: "<consequence>" } ] } ] }) ``` Batch rules: at most five questions, two to five mutually exclusive options each, recommende