Ask Silva

You don't remember every skill, so ask.

A flow is a path through the skills. Most paths run along one main flow, and two on-ramps merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.

Output contract

Every chat reply and every artifact these skills produce (spec, ticket, brief, handoff, report) is written in the /unglaze voice: conclusion first, one idea per bullet, no repetition, nothing that doesn't carry information. Budgets on top of that voice:

• Chat reply: 150 words, three findings or options. More exist? Say how many and stop.
• Artifact over 300 words: opens with an At a glance block of at most 100 words: problem, decision or status, next action.
• Lists: the smallest complete set of non-overlapping items. Never "extensive".

Brevity compresses structure and repetition, never substance: risks, acceptance criteria, negations, and unresolved decisions survive verbatim. Two skills below (/to-spec, /handoff) are silvabyte forks that bake this contract into their templates; the rest are upstream and rely on this section.

The main flow: idea → ship