← ClaudeAtlas

pythia-speclisted

Use when the developer asks to build or change something and the request leaves real decisions open - a new feature or flow ("build X", "lam luong Y", "them chuc nang Z"), a behaviour with more than one reasonable shape, a security or audit trade-off, or scope that could be read two ways. The request arrives as plain words, not a command - this skill fires on the words. Surface those decisions as questions with options and trade-offs, get them settled, and only then move to impact and write. Also use the moment you catch yourself choosing a business behaviour mid-implementation that the developer never stated.
thaildhe172591/pythia · ★ 4 · AI & Automation · score 77
Install: claude install-skill thaildhe172591/pythia
# Settling the Spec **Announce at start:** "Using pythia-spec — this request has open decisions that are yours, not mine." **Phase:** Learn → Ask — learn enough to ask well, ask until the spec is settled, and only then build The other skills are the construction chain: they start after the spec is settled. This skill owns the moment before — because an agent that quietly settles the spec itself will build the wrong thing *fluently*, and the developer's first chance to disagree arrives after the code exists, when every choice costs a rewrite. ## The Iron Law ``` SPEC DECISIONS BELONG TO THE DEVELOPER. YOU PROPOSE; THEY CHOOSE. ``` ## Spec or technical? The line that decides who decides | Spec — ask first | Technical — decide yourself, cite your source | |---|---| | What is stored: new table vs new columns, what is kept vs deleted | Names and shapes — the conventions already decide them | | Business behaviour: expiry times, retry limits, lockout counts, who is allowed | Which dictionary view or query answers a question | | Security ↔ audit trade-offs: delete the token vs keep the trail | Following an existing pattern found via `similar` | | Channels and scope: email or SMS, which tenants, which callers | Datatype dictated by the house rules for that kind of value | | Deviating from a mandatory convention | Anything `pythia conventions` or the codebase answers | Rule of thumb: **if two senior developers could reasonably ship different behaviour, it is spec.** If the code