Skip to content

Skill

Spec

gstack

Turns a vague intent into a precise, buildable specification, working through the ambiguities in stages until the requirements are concrete enough to implement against. It assumes you have decided WHAT you want and need it made executable - not whether the idea is worth doing, and not a critique of a plan you already drafted.

Situations it fits

Engineers asked for exact UI states, API fields, and edge-case behavior for a new feature - they need the details so they can start coding.
Spec. spec is built to convert a decided feature into precise, implementable requirements - the exact screens, inputs, and edge cases engineers need. The other options are for critiquing plans, testing nascent ideas, or reviewing past work, not producing detailed implementation specs.
Product and design agreed on a headline feature but disagree about edge cases and API validation; the engineering manager asked you to produce the authoritative, unambiguous spec they can build from.
Spec. Spec is intended to resolve ambiguity by documenting exact behaviors, inputs, and failure modes so engineers have a single source of truth. The other skills deal with assessing plans, interrogating new ideas, or reviewing past work, none of which produces the concrete implementation document required here.

3 scenarios in the bank answer to Spec. The rest are in the game.

Skills it gets confused with

These share a family with Spec, which is another way of saying they are the ones you might reach for by mistake.

Knowing what Spec does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Spec is part of garrytan/gstack. Licence: MIT. The description above was written for this game, not taken from the skill.