canopy

Check whether this card's code meets the acceptance criteria

Run a quick UX/UI workshop using ASCII-art sketches

Write automated tests for unticked scenarios in this card's test cases

Review code changes on this card for likely bugs, regressions, and missed edges

Cherry-pick post-merge commits onto a new follow-up branch

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.

Audit this card's mockups or implementation against the design library

Draft or refine the project's PRD from the description and conversation

Draft edits to existing specs (or a new spec if no existing one fits) from the card description

Draft or refine the test-cases checklist for this card

Pull remote changes and reconcile with local work, checking for soft conflicts

Rebase onto latest upstream, checking for soft conflicts

Generate a context-rich briefing prompt for an external agent (Claude Code, Cursor, etc.)

Implement this card

Interview me about this card to develop the acceptance criteria

Diagnose and fix the bug described on this card

Produce an HTML mockup for the UI being discussed

Workshop how to break this card into smaller spawned cards and capture entries in the card plan

Draft or refine the implementation checklist from specs and current code

Fresh-eyes review of the project's PRD for gaps, contradictions, vague phrasing, and unresolved decisions

Drive the card's Review Hero loop by hand — trigger a review, address its comments, rerun until clean, then merge. Use in an external tool (Claude Code, Cursor) where Workhorse's automated loop isn't running.

Review implementation for common security vulnerabilities

Review this card's specs with fresh eyes for gaps, contradictions, and cross-spec impact

Split a working doc into the card's specs, plan, and test cases once its shape is clear

Start a working doc — a drafting space where spec-level and implementation thinking co-exist before splitting into specs, plan, and test cases

Run a support investigation as a suggest-and-interpret loop, never executing anything yourself — orient to the product's support pack and follow the signal with judgment. Use when someone asks for help triaging, investigating, or resolving an operational or support issue on a deployment. Not for feature-development cards (see investigate-and-fix and implement-this).

Workshop the technical approach and capture notes in the plan

Produce or refine a project-level mockup illustrating a section of the PRD

Workshop the shape of this project — audience, components, ambiguities — before drafting the PRD

Workshop this idea with me