Spec

Goal

Turn what you and the user have been discussing, or the user's idea, into a single self-contained spec — part PRD (user-facing intent), part technical spec (decisions already settled).

Hard Rules

• Before drafting, grill the user on the open technical decisions (see Flow → Grill the technical decisions) — material choices the conversation left unresolved that the codebase can't settle. Outside those, if a gap blocks the writeup, resolve it and note the assumption rather than reopening the interview.
• Placeholder language. No TODO, TBD, for later, v2, "we'll figure out later", or equivalent. If a decision is open: resolve it now (one targeted question or spawn a subagent to investigate), or move it to Out of scope with a sentence on why.
• Every subagent this skill spawns runs at the standard tier (see References → Subagents) unless otherwise specified.
• Write the draft to a fresh OS temp file: $(mktemp -t crank-spec).md. Do not write into the working directory unless the user explicitly asks. Tell the user the path once.
• Reference real files as path:line wherever you have them.

Guidelines

• Synthesize from the conversation; don't re-litigate what's settled.

Simplify first