Make the Jira skills call unslop, grilling, and tdd where they pay

All three already delegated in places — ticket calls diagnosing-bugs and
run, review-ticket calls codebase-design — so this extends a habit rather
than starting one.

unslop is the load-bearing part, at four points: create-ticket before the
Jira write, review-ticket's check list where a bare punctuation sweep
stood, and ticket on both mr.md and the Jira fields. Every one is scoped
to pattern detection and skips the "Adding soul" section, which is blog
voice and would fight the rigid house formats. The mr.md hook exempts the
pasted pre-MR handoff, generated output the skill already forbids
editing, and the field hook exempts proof cells. Conrad and Henry read
all of this, and prose that reads as machine generated costs the work its
credibility before anyone weighs what it says.

grilling comes in as a classification gate rather than blanket ceremony.
ticket now names the work bounded or architectural before drafting
plan.md and escalates only on architectural, where a wrong assumption is
expensive to find in Phase 2; bounded stories go straight through as
before. create-ticket escalates only when the epic docs have not settled
scope, which is where invented scope gets in.

tdd is gated the same way: test-first for procedures, derivations,
permission checks, migrations and state machines, and explicitly not for
UI wiring or copy changes, where it would produce the smoke-test padding
House style rejects. That closes a loop already half built, since
review-ticket proposes automated-test subtasks — those subtasks now name
the behavior to demonstrate, and ticket writes them first.
codebase-design gets the same call in ticket's planning step that
review-ticket already makes.

No steps were renumbered, so ticket's Phase 2 cross-references still
resolve.

Claude-Session: https://claude.ai/code/session_01DFgQVLdzLwu56gU8m4gvCS

user/agents/skills/create-ticket/SKILL.md

@@ -61,7 +61,20 @@ Same conventions as the `/ticket` skill:
    and offer to draft a questionnaire with `/to-questionnaire` so it can go to that
    person in one pass. If Gib would rather ship the story without waiting, the question
    becomes a numbered Note naming its owner.
+   Where the scope of the story itself is unsettled, meaning the epic docs, the
+   deliverables, and the code do not already say what this ticket covers, one question
+   is not enough and drafting anyway is how invented scope gets in. Call the Skill tool
+   with "grilling" and work its frontier with Gib until the scope is agreed, then draft.
+   This is the exception rather than the default. Most stories have their scope already
+   worked out in the epic docs, and those go straight to step 4.
 4. **Draft the content** in the matching format below, in markdown first.
+   Then call the Skill tool with "unslop" and apply its pattern detection to the
+   draft: puffery, superficial -ing phrases, "not just X but Y", vague attributions,
+   rule of three padding, alongside the punctuation rules above. Skip its "Adding soul"
+   section entirely. The house formats are rigid templates and an AC table does not
+   want voice, it wants to read as though a person wrote it plainly. Conrad reads these,
+   and prose that reads as machine generated costs the ticket its credibility before
+   anyone weighs what it actually says.
 5. **Overwrite guardrail.** If the ticket already has a non-trivial description
    (anything beyond a placeholder), show what is there and confirm before
    replacing it. Empty or placeholder tickets are filled without asking.