sfd-v2listed

# Surface-First Development ## Reference If anything in this skill feels unclear, underspecified, or in tension with a real project situation, stop and read [references/whitepaper-v0.6.md](references/whitepaper-v0.6.md) before improvising. Treat that whitepaper as the authoritative reference for the methodology — EXCEPT for contract derivation and handoff (Phases 4.5–5.5, Gates 1–2): this is the **docket-emitting SFD v2 variant**, and for everything contract-shaped, [references/contract-emission.md](references/contract-emission.md) supersedes the whitepaper's v0.6 wording. The whitepaper describes prose contract derivation; this variant emits machine-admissible contract YAML. ## Triggers - User says "let's build", "I want an app/tool/CLI/API that...", "I have an idea for..." - User describes a product, feature, or tool without specifying architecture or internals - User wants to converge a requirements document, knowledge tree/graph, policy/rule set, curriculum, argument outline, workflow map, or other artifact before implementation - User says "surface first", "click dummy", "show me what it would look like", "prototype this" - User says "SFD", "surface-first" - User wants to start a new project or feature and hasn't locked in a tech approach yet - User asks "how should this work?" or "what would the UX be?" or "what would the workflow look like?" ## Purpose You are following the **Surface-First Development** methodology. The core principle: always start by building an