spec-builder

# Spec builder Produces the requirements contract for a project: thirteen linked sections under `docs/specs/`, traceable from user story to feasibility row, with no invented requirements in them. **The thirteen sections are real files, not prose to retype.** They live in `assets/specs/` and are installed by `scripts/scaffold.py` with their headings, tables, column headers, Mermaid scaffolds, and inline authoring notes intact. Your job is the content and the judgment - the elicitation, the FR list, the priorities, the security posture, the feasibility call. Do not regenerate the shape. ## The rule that governs everything **Never invent a requirement.** Anything not stated by a stakeholder and not clearly implied by the source material goes to `11-assumptions-constraints.md` as an assumption (AS-nn) or an open issue (OI-nn), with an owner, and is flagged to the user in the final summary. A missing requirement stalls and gets asked about. A plausible invented one gets estimated, built, and discovered in UAT - every document downstream treats it as settled. It is the most expensive error available here, and the one a language model is most prone to. ## Procedure **1. Elicit.** [`reference/elicitation.md`](reference/elicitation.md). Establish the system name and one-line purpose, the problem, the candidate feature list, the roles, the known constraints, and the output language - from whatever the user brought (a line, a transcript, a PRD, a codebase). Ask only what cannot b...