Extract a Spec from a Conversation

A feature without a written spec is a feature that drifts. Drift is when the engineer's interpretation diverges from the asker's intent — discovered three weeks in. This skill converts conversation into a spec that pins down the contract.

When to use

• Stakeholder said "just build X" with no written requirements.
• Requirements live across multiple Slack threads / meeting notes.
• Engineer is about to start a multi-week feature without a spec.
• Bug ticket that's actually a feature ask in disguise.
• Mid-implementation realization that the spec is ambiguous on a key point.

When NOT to use

• Trivial changes (typo, lint, single-file fix).
• Already have a spec — propose edits, don't rewrite.
• Discovery / research — spec comes after, not before.

The spec template