acceptance-audit
FreeCheck whether this card's code meets the acceptance criteria
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026
FreePublished on GitHub
start-working-doc
Start a working doc — a drafting space where spec-level and implementation thinking co-exist before splitting into specs, plan, and test cases
The English summary is being prepared. Showing the original description.
See how to installFiles included (1)
- SKILL.md1.7 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
Your task: Start a working doc
If you don't already have this card's context (title, identifier, description) — for instance when running outside Workhorse — establish it first by following .agents/docs/card-context.md.
Scaffold a new working doc for this card. A working doc is a per-card drafting space where spec-level and implementation thinking co-exist before the card is split into its long-lived artefacts. It suits larger, epic-level cards; most cards don't need one.
- Read
.agents/docs/working-doc-format.mdfor the shape and voice of a working doc. - Create the file at
.workhorse/working-docs/{card-id}/working-doc.mdwithstatus: draftfrontmatter, an H1 title derived from the card, and a one-line overview. Keep it minimal — do not pre-draft the body sections. - Invite the user to keep talking — workshopping behaviour and implementation together — and accrue that conversation into the working doc under the sections in
.agents/docs/working-doc-format.md, rather than letting it flow into specs or the plan. Mention Split working doc as the move for when the shape is clear.
Do not start interviewing or drafting body content from this skill — creation only.
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
Summarise the unit and e2e tests a branch/PR adds, run only those, and produce a paste-ready report (e.g. for a Linear card). Use when asked to 'summarise added tests', 'run the new tests', 'what tests did this PR add', or to prove a card's test coverage.
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026
ascii-design
FreeRun a quick UX/UI workshop using ASCII-art sketches
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026
Write automated tests for unticked scenarios in this card's test cases
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026
bug-review
FreeReview code changes on this card for likely bugs, regressions, and missed edges
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026
Maintain a support docs pack — dedup, length budgets, and no splintering — and land changes as a reviewed pull request. Use when a support thread, or a hand-off from Support assist, surfaces a new resolution, a correction to an existing one, or a deployment quirk worth recording. Not for ordinary code changes.
The English summary is being prepared. Showing the original description.
beyondessential/tamanu9Updated Oct 20, 2026