ilk-speclisted

# ilk-spec — spec-elaboration front-stage A planning *pre-stage* that runs BEFORE `/ilk-plan` for tasks that are too thin to decompose, where the missing detail is **domain knowledge nobody can hand you off the top of their head**. It researches how this class of thing is normally built, drafts a design, attacks that design, gets your sign-off, and hands a thick, tier-tagged task description to `/ilk-plan`. This stage produces a **spec**, not code and not a plan. Decomposition is `/ilk-plan`'s job; execution is the loop's. ## When to use (gate — read first) Use ONLY when BOTH hold: - The task is **thin / under-specified**, AND - the missing information is **domain/industry knowledge** (how this class of thing is normally built), NOT details living in the user's head. Skip this stage when: - The user CAN answer clarifying questions (which repo, which auth, which deadline) → go straight to `/ilk-plan`, which already asks 1–3 clarifying questions for thin-but-answerable input. - The task is already well-specified → go straight to `/ilk-plan`. This stage costs extra model time (research + a critique pass). It is **opt-in**, for the domain-gap case only — never a default pre-step on every plan. ## The principle `/ilk-plan` handles thin input by *asking the user*. That fails when the user isn't the source of the missing knowledge. This stage fills the gap a different way: **research the conventions, draft a design, then attack it** — and only then hand a thick spec