To Spec Plus

Take the current conversation context and codebase understanding and produce a spec (a PRD). Do not interview the user — the interview already happened (usually a grill-me-plus session); this skill synthesizes it.

If a load-bearing decision is genuinely unresolved — one the spec cannot be written without — don't guess and don't launch a full interview. Ask just that decision through AskUserQuestion (recommended option first, trade-offs per option), or suggest a grill-me-plus round if several are open.

Pipeline position: grill-me-plus/wayfinder-plus (decide) → to-spec-plus (record) → to-tickets-plus (slice) → implement-plus (build).

Process

1. Explore the repo

Understand the current state of the codebase if you haven't already. Use the project's domain vocabulary throughout the spec (read CONTEXT.md if one exists — domain-modeling-plus maintains it) and respect any ADRs in the area being touched.

2. Sketch the test seams

A seam is the public boundary the feature will be tested at (codebase-design-plus holds the full deep-module vocabulary). Prefer existing seams to new ones, and the highest seam possible — the fewer seams across the codebase, the better; the ideal number is one.

The Laravel seam ladder, highest first: