Skip to content

mikeparcewski/wicked-garden / skills/draft

wicked-garden-draft

Verified

The 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).

FileKindSize
SKILL.mdskill md14.0 KB
refs/claims.mdmarkdown4.7 KB
refs/demo-script.mdmarkdown1.9 KB
refs/design-floor.mdmarkdown4.8 KB
refs/meeting-prep.mdmarkdown1.9 KB
refs/message.mdmarkdown1.6 KB
refs/narrative.mdmarkdown1.9 KB
refs/operating-model.mdmarkdown2.1 KB
refs/respond.mdmarkdown3.9 KB
refs/rework.mdmarkdown4.1 KB
refs/self-check.mdmarkdown7.0 KB
refs/status-update.mdmarkdown1.7 KB

refs/status-update.md

View on GitHub
# Kind: status update

A periodic report on where the work stands: what got done, what is next, and what needs help. The
brief's `Kind: status update.` line selects this ref. The skill's three floors still apply.

## Shape

1. **Header:** the project, the period it covers (absolute dates, `2026-11-02 to 2026-11-06`), and
   the author or team.
2. **In three lines:** the overall state, the most important thing that happened, and the most
   important thing needed from the reader.
3. **Done:** each item with its evidence (a merged pull request, a release, a closed issue, a
   finished run), cited.
4. **In progress:** each item with what is left and the expected date, if the sources give one.
5. **Next:** the planned items for the next period.
6. **Risks and blocked:** each with its impact, the owner, and the specific ask (who, what, by when).
7. **Numbers,** only when the sources carry them, with their period.

## Rules

- **Evidence or it did not happen.** A done item cites the change or record that shows it; an item
  you cannot cite is "in progress" or left out.
- **A red/amber/green status only with its rule.** Use one only when the brief or the sources state
  what each colour means; otherwise describe the state in words.
- **Dates are absolute.** Never "yesterday" or "next week"; a reader opens this later.
- **Bad news is in the first three lines,** not buried under Done.
- **Sized:** one page unless the brief names a budget (self-check `--pages 1`).

## Never

- invent progress, a percentage complete, or a date the sources do not give;
- list activity as achievement ("worked on X") without saying what changed;
- leave a blocker without an owner and an ask.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall