goal-speclisted

<!-- Copyright (c) 2026 JG Systems Consulting Ltd. MIT License (see LICENSE). --> # Goal Spec Convert a **goal** into a **complete engineering specification**. The goal-formatter answers *"what does done look like?"*; this skill answers *"what exactly are we building, and how?"* — by defining every section of the spec and **asking the user gap-filling questions** wherever the goal leaves a section under-determined. This is the **middle skill** in a three-skill chain: ``` goal-formatter → goal-spec → spec-review (goal + draft (THIS: full (autonomous spec, optional) defined spec multi-discipline via Q&A) hardening loop) ``` Each skill is independently invocable. The handoff works because all three use the **same 8-section engineering spec template** (defined below — this skill owns it). ## When to use **Trigger phrases:** - "Spec this goal" / "Write a spec for X" - "Define the specification" / "Flesh out the spec" - "Turn this goal into a spec" - "I have a goal, now I need the detailed design" **Best for:** - A goal that's clear on *done* but vague on *how* / *what exactly* - Work where requirements, constraints, and design approach need to be pinned down before coding - Producing an artifact you'll then harden with `spec-review` ## Inputs this skill accepts 1. **A goal** (e.g. the output of goal-formatter) — most common. 2. **A goal + draft spec** (goal-formatter's spec mode output) — this skill *completes and refine