mikeparcewski/wicked-garden / skills/draft
wicked-garden-draft
VerifiedThe quality floor for DOCUMENT deliverables drafted from a repo — brochures, one-pagers, flyers, pages, decks, memos — guidance plus a self-check before "done". Three floors: (1) READABLE — every text/background pair ≥ 4.5:1 (WCAG AA; 3:1 for large text) on COMPOSITED colours, print text ≥ 7pt; (2) SIZED TO THE BRIEF — the RENDERED page count honours the brief's page budget; (3) GROUNDED — every number, URL and claim cites a repo path, mocks visibly labelled, no placeholder ships. Use when: "draft a brochure / one-pager / page / deck / memo about <repo>", "print-ready A4 / Letter", "make it two pages", "is this brochure readable / grounded", before declaring a wicked-interactive draft/edit/revision done, or as the skill a governed drafting run (wicked-crew `interactive-*`) follows. A brief's `Kind:` line (narrative, status update, message, …) adds that kind's ref. NOT for code documentation (the engineering documentarian) or a running app's accessibility audit (the product or qe a11y skills).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.0 KB |
| refs/claims.md | markdown | 4.7 KB |
| refs/demo-script.md | markdown | 1.9 KB |
| refs/design-floor.md | markdown | 4.8 KB |
| refs/meeting-prep.md | markdown | 1.9 KB |
| refs/message.md | markdown | 1.6 KB |
| refs/narrative.md | markdown | 1.9 KB |
| refs/operating-model.md | markdown | 2.1 KB |
| refs/respond.md | markdown | 3.9 KB |
| refs/rework.md | markdown | 4.1 KB |
| refs/self-check.md | markdown | 7.0 KB |
| refs/status-update.md | markdown | 1.7 KB |
refs/message.md
View on GitHub# Kind: message
A short message for one channel: an email, a chat post, an announcement, a reply. The brief's
`Kind: message.` line selects this ref. The skill's three floors still apply; a message is a screen
deliverable with no page budget.
## Shape
1. **Subject or first line:** the point in under ten words (for chat, the first line is the subject).
2. **The ask or the news** in the first sentence: what you want the reader to do, by when, or what
changed for them.
3. **Context:** two to four sentences, each fact cited (a link to the pull request, the run, the
document).
4. **The ask again,** with its date, when there is one. One ask per message.
5. **Sign-off** in the channel's convention.
## Rules
- **Short:** under 150 words unless the brief asks for more. Cut context before the ask.
- **The channel sets the tone.** Chat: plain, no greeting block, a list only for three or more
items. Email: a greeting and a sign-off. An announcement: what changes, for whom, from when, and
where to ask.
- **Links are cited claims.** Each one goes to the source the claim comes from, written out or as
link text that says where it goes ("the release pull request"), never "here".
- **Unknown recipient:** write without a name rather than a `[Name]` placeholder; the floor fails a
placeholder.
- **Self-check:** `--no-pages --min-font-pt 0 --mode screen`.
## Never
- send, post or schedule it: this is a draft for a person to send;
- promise a date, a fix or a commitment the sources do not show;
- put a credential, a private address or internal-only detail in a message meant for outside readers.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |