Menu
Workshop the technical approach and capture notes in the plan
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | tech-design |
| description | Workshop the technical approach and capture notes in the plan |
| label | Tech design |
| pill-order | {"specifying":7,"implementing":4} |
| jockey-hint | Good fit when the user wants to talk through technical tradeoffs before committing to implementation. Demote once substantial tech notes are already in the plan unless the user signals a fresh area to workshop. |
| workhorse-version | 0.2.0 |
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.
Workshop the technical approach for this card interactively. The goal is to capture rationale, tradeoffs, and decisions into the card's plan file as prose notes.
.workhorse/plans/{card-id}/.workhorse/plans/{card-id}/plan.md — an H1 title, an optional summary, and sections of notes are enough for a first versionWhere notes land: if a working doc exists for this card in draft status (.workhorse/working-docs/{card-id}/working-doc.md), write your notes into it — under the conventional sections in .agents/docs/working-doc-format.md — rather than the plan. The working doc is the drafting home while the card is being shaped. With no draft working doc, write to the plan as usual.
The plan is a free-form working document, not a spec. It can carry a mix of tech design notes, refinement notes, and (later) a checklist of steps — see .workhorse/specs/plan/overview.md for the shape.
Do not start implementation from this skill. This skill is for thinking and note-taking only.