writing-nebu-skillslisted

# Writing Nebu Skills Two modes: (1) create or revise skills that improve agent judgment, (2) capture reusable workflow gaps observed during sessions. ## Creating skills ### Design rules 1. The description says **when to use**, not how the skill works. 2. Keep common skills short enough that loading them is worth it. 3. Prefer one clear pattern over a long manifesto. 4. Add support files only when the main file would become reference-heavy. 5. Make autonomous progress the default when the goal is clear. 6. General skills should not hardcode branded artifact trees or repo-local folder conventions. 7. Encode hard gates only for failures that are expensive and common. ### Design test - What mistake will the model make without this skill? - What is the smallest guidance that prevents that mistake? - Does this skill help discovery, or does it just add ceremony? ## Capturing workflow improvements When agent behavior reveals a reusable gap: 1. State observed gap: what was missed, guessed, repeated, or done too late. 2. Propose smallest durable fix: skill text, router hint, plugin behavior, or issue-flow guidance. 3. Prefer updating an existing skill over creating a new one. 4. If implementing immediately, still create or reuse a tracking issue in the skill-pack source repo. 5. If not implementing now, create follow-up issue with evidence and concrete proposed fix. ### Hooks 1. After review or verification, check whether session exposed reusable workflow gap. 2. If yes, lo