Mariomarquezt/multi-flow-skills / skills/multi-model-fix
multi-model-fix
Verified| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 25.0 KB |
| templates/checker-brief-standard.md | markdown | 2.9 KB |
| templates/cross-check-brief.md | markdown | 2.4 KB |
| templates/fix-brief.md | markdown | 3.4 KB |
| templates/item-file.md | markdown | 1.4 KB |
| templates/lean-brief.md | markdown | 2.6 KB |
| templates/lean/bg-run.shexecutable | script | 979 B |
| templates/lean/gate-example.sh | script | 989 B |
| templates/lean/lean-collect.shexecutable | script | 2.3 KB |
| templates/lean/lean-group.shexecutable | script | 4.7 KB |
| templates/lean/lean-mkcheck.shexecutable | script | 2.1 KB |
| templates/lean/lean-run.shexecutable | script | 2.0 KB |
| templates/lean/lean-wait.shexecutable | script | 1.4 KB |
| templates/repro-brief.md | markdown | 2.0 KB |
| templates/scout-brief.md | markdown | 1.7 KB |
templates/item-file.md
View on GitHub# Item {{ID}}: {{TITLE}}
The lead writes this file ONE time per item. The sub-task brief, the repro brief and the check
brief use it. Nobody edits it after the first dispatch (a change = a new line `CHANGED <date>: ...`
at the end, and the checker is told).
## Claim / wish (verbatim from the source)
{{TEXT, with the sequence of events it describes}}
## Done lines
- D1: {{what is true when this item is done, one fact per line, with the exact message or value}}
- D2: {{...}}
## Test list (one test per line)
- T1 refusal: {{case}} -> {{exact message / value}}
- T2 success: {{case}} -> {{value that comes back}} + {{side effects that must happen}}
- T3 failure side effects: {{case}} -> {{what must NOT run: audit, redirect, write}}
- T4 edge input: {{empty | array | null | over the limit}} -> {{result}}
(or one line: `NONE: type-only change` | `TEST-ONLY: the tests are the change; break: <...> -> <test> fails`)
(a proof that is a COMMAND RUN, not a test case: `T5 run: <command> -> <expected output>`; the lead
runs it in the gate and its output goes in the gate file, so that the checker sees it)
## Seam / contract (verbatim, if this item uses or makes a shared interface; else delete)
{{types, function signatures, exact messages}}
## Must not break
{{public contract, data, behaviour a test pins}}
## Map (from the scout; `scout says` = the lead did not open it)
{{path:from-to; function; callers; tests; throws; db}}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |