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/narrative.md
View on GitHub# Kind: narrative
A narrative tells one story about the work: why it exists, what changed, and what it means for the
reader. The brief's `Kind: narrative.` line selects this ref. The three floors in the skill (readable,
sized to the brief, grounded) still apply; this ref adds what a narrative needs.
## Shape
1. **The point, first.** One or two sentences a reader could repeat: what happened or what we
propose, and why it matters to them.
2. **Situation.** Where things stood, in facts the sources carry.
3. **Complication.** What made the situation untenable or the opportunity real, with evidence.
4. **Resolution.** What was done or is proposed, and how it addresses the complication.
5. **Proof.** What shows it works or will: measurements, shipped changes, a user's words, each
cited. When there is no proof yet, say what would count as proof.
6. **The ask or the next step,** when the brief names an audience who must act.
## Rules
- **Name the audience** from the brief (executives, engineers, customers) and write for them: an
executive narrative leads with the outcome and the cost; an engineering one with the mechanism.
With no audience named, write for an informed outsider and say so in `notes.json`.
- **One story.** A second storyline is a second document; cut it or mention it in a line.
- **No claim without a source.** Adjectives are claims too: "fast", "secure", "loved" need a cited
number or a quote, or they go. A story that the sources do not support is not told.
- **Plain words, short paragraphs** (three to five sentences), active voice, no jargon the audience
would not use.
- **Sized:** one page unless the brief names a budget (self-check `--pages 1 --exact`). Cut
sections, not the point.
## Never
- invent a customer, a quote, a date or a number to make the story land;
- pad with a history the reader does not need to follow the point;
- end without the point restated in the last paragraph, or without the ask when there is one.
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 |