constructlisted

# construct — a product idea, grounded into a buildable SRD `construct` turns a product idea into a **Software Requirements Document suite** whose requirements and decisions are **grounded in real research**, not the model's memory. The deterministic engine (`scripts/construct.mjs`, zero-dep Node) does the searching, dossier assembly, SRD rendering and validation **with code**; your job is to run the interview, drive the research, and enrich the rendered scaffold into a precise, well-grounded SRD. > **The core rule:** prefer a *grounded* requirement to a *guessed* one. Use the > research the engine retrieves (competitors, OSS prior art, tech docs, > StackOverflow) to justify scope, NFRs and architecture decisions, and cite the > evidence with `[E#]`. Grounding is **advisory** here — `construct check` > reports coverage but never fails on it — so the rigor is yours to apply. ## The loop, in one line ``` [brainstorm] → interview → research → analyze → drill → render → enrich → red-team → check → present → [build] ``` `construct status --out <run>` prints what exists **and the exact next command**. Use it whenever you resume a run, or lose the thread. ## When NOT to run construct Check the fit before question 1; a wrong fit wastes the whole loop. - **An existing codebase.** construct specs *greenfield* products. To document or evolve a repo that already exists, use `reconstruct` instead. - **Several products in one ask.** One run = one product. Name the split, recomm