Idea to Spec

Turn the idea into a technical spec covering goals, non-goals, constraints, entrypoints, changes to existing behavior, failure handling, open questions, and how each claim will be verified — not implementation steps.

Ground every factual claim in evidence you gathered from the codebase or environment this session, and put decisions that are genuinely the user's — anything involving auth, credentials, destructive operations, cost, or taste — to the user rather than defaulting them.

Spend as much computation as the stakes warrant: explore widely, draft alternatives, critique your own draft with fresh eyes, and iterate until the spec would survive a skeptical reviewer.

Confirm the spec with the user before publishing it wherever they choose.