workinggenius plugin
A development workflow that walks every piece of work through the six Working Geniuses — Wonder, Invention, Discernment, Galvanizing, Enablement, Tenacity — every stage a command the user types, every checkpoint a live exchange.
How to install the workinggenius plugin
Run both commands inside Claude Code. The first adds the marketplace once; the second installs the plugin.
/plugin marketplace add donald-ada/workinggenius
/plugin install workinggenius@workinggeniusWhat's inside workinggenius
23 parts read from the plugin's own files.
Skills 23
Claude loads it when the task matches- architect
Answer build-or-adopt honestly, then design one committed architecture from your own understanding of the problem — driven by ranked quality attributes, stress-tested against the field and against change, proven by a walking skeleton, its consequences confirmed by the user, committed to ARCHITECTURE.md. A command the user types, for greenfield or architecture-shaping work; standalone, no other skill required.
- attack
Put a plan, a design or a set of approaches the user hands over under blind attack, one attacker per path, and report what broke each and what each survived. User-invoked only, and outside the flow, so nothing is tracked and no work file is written.
- blindspot
Find the unknowns before they find the work — a read-only territory pass that surfaces the questions nobody knew to ask, judgment taught before a choice is extracted, and a quiz that catches the user's map up with what actually changed. Use when work enters territory the user calls unfamiliar, when the user is confirming a choice they can't evaluate, or when the user asks what they're missing or wants to be quizzed before accepting built work.
- compact
Put the compaction question to a snapshot that drifted — route what no longer constrains unfinished work, and say what moves before moving it. In flight or done; the log is appended to, never edited or trimmed.
- decision-record
Keep the index of the project's settled decisions in .genius/DECIDED.md — one line per decision, pointing at the fight that settled it, earned by one test: would a future stranger re-fight this? Use when such a decision lands, when a design might contradict a settled one, or when another skill needs the index discipline.
- designer
Settle the look before the pixels — audience and context first, then the base and the delta, directions drawn as tiles from a written brief and a critic's read of the chosen one, accessibility as the floor, one design language committed to DESIGN.md as tokens with roles. A command the user types, for work with an interface someone will see; standalone, no other skill required.
- diagnose
Debugging as the six geniuses at minute scale — the bug confirmed by a red reproduction before any theory, hypotheses plural with kill-reasons before any fix, the fix proven by a fresh green rerun. Use when something is broken, throwing, failing, flaky, or slow, or when the user asks to debug or diagnose.
- discern
Explore the paths first where none are on record (the `invent` skill), then attack every path adversarially with one blind attacker per path, commit to one, and present the commitment — consequences for the user to confirm, kills on the record. Use when the user asks to run discernment on a tracked piece of work (`/discern`, or in words), or asks for a ready-made plan to be attacked before it is built. A work whose `next:` names this stage is not that ask, because the flow never advances itself, and a plan handed over to be implemented is not an invitation to attack it or to start the flow.
- domain-glossary
Maintain the project's shared vocabulary in CONTEXT.md — challenge conflicting terms, sharpen fuzzy language, record resolutions inline. Use when a term being settled with the user conflicts with the glossary or means two things, when a decision names a new project concept that later work will need a word for, or when another skill needs the glossary discipline. Reading CONTEXT.md to use its vocabulary is not this skill, and an ordinary request that uses a term is not an invitation to start a glossary.
- enable
Build one slice at a time with red-before-green tests at the agreed seams, tight feedback loops, and fresh-eyes review at every slice close. Use when the user asks to build a tracked piece of work or one of its slices (`/enable`, or in words) — including small work that never cut slices, built against its confirmed problem. A work whose `next:` names this stage is not that ask, because the flow never advances itself.
- errata
Correct what was written wrong — the binding line rewritten in place, the record it came from appended to and never touched, both carrying the evidence that overturned it. Use when a run, a file, or the user contradicts something already written in a work file, a plan's contract, the glossary, or the decision index; when a pinned value or a stated fact turns out not to hold; or when another skill needs the correction discipline.
- fresh-eyes
Have a diff reviewed by a reviewer with no memory of how it was written, judged against what the user says it should do, and report what it would block on with evidence. User-invoked only, and outside the flow, so nothing is tracked and no work file is written.
- galvanize
Turn the chosen design into mobilized work — a brief, vertical slices with acceptance criteria, and agreed test seams. Use when the user asks to run galvanizing on a tracked piece of work (`/galvanize`, or in words). A work whose `next:` names this stage is not that ask, because the flow never advances itself.
- genius
The map of the Working Genius workflow — where each piece of work stands, what to run next, and where genius gaps are hiding.
- genius-file
Read and update Working Genius work files — the work's folder holding the bounded snapshot a cold session acts on, the append-only log behind it, and the contract that binds the unbuilt slices. Use when a stage skill needs the work-file discipline, when the user asks what work is in flight or where a piece of work left off, or before resuming any work tracked under .genius/.
- invent
Genuinely explore structurally different approaches before committing — the alternatives exist to be beaten, not to be presented. Runs as the first half of `/discern` when the work has no paths on record yet; used on its own when the user asks for invention alone on a tracked piece of work (`/invent`, or in words). A work whose `next:` names a stage is not that ask, because the flow never advances itself.
- reconcile
Check the project's binding documents against the repo they describe — settled decisions, glossary terms, pinned commands, in-flight plan contracts, the links between file and record — and route every drift to its correction.
- record-prose
How the flow's records are written — every document under .genius/, snapshot to backlog line. Use when writing or rewriting any of them, or when another skill needs the prose discipline.
- setup-working-genius
Per-repo configuration — pin the work-file directory, verify commands, and issue tracking, seed the project docs, and leave the pointer that tells every future session this project works this way.
- tenacity
Drive the work to actually-done — fresh verification of every claim, context-isolated diff review, cleanup, commit, post-mortem. Use when the user asks to close out a tracked piece of work (`/tenacity`, or in words), whether it moved through slices or was built directly after Wonder without them. A work whose `next:` names this stage, or whose last slice just closed, is not that ask, because the flow never advances itself.
- triage
Put the backlog's own rules to the backlog — seeds that should no longer be there, pairs that are one discovery, seeds that outgrew a line, and the order nobody has stated. Judged one at a time, landed only by the user's call.
- waitwhat
Explain what was just said, and why it is being done this way, in plain everyday words a newcomer can follow — the problem it solves, what goes wrong without it, what was given up. User-invoked only; only the reader knows when understanding broke.
- wonder
Question the work before doing it — the interview that turns a raw idea into a confirmed problem statement. Use when the user asks to run the interview on a tracked piece of work (`/wonder`, or in words), or when the user asks to start the Working Genius flow — or to be questioned — on a new idea. An ordinary request to build something is not an invitation to start the flow.
Using workinggenius in Claude Code
Skills need no command. Claude reads them when your request matches what they describe.
Update, turn off or remove
- Update the plugin (shell)
- claude plugin update workinggenius@workinggenius
- Refresh the marketplace
- /plugin marketplace update workinggenius
- Turn it off for now
- /plugin disable workinggenius@workinggenius
- Remove it
- /plugin uninstall workinggenius@workinggenius
Skills in workinggenius
- enabledonald-ada/workinggenius
Build one slice at a time with red-before-green tests at the agreed seams, tight feedback loops, and fresh-eyes review at every slice close. Use when the user asks to build a tracked piece of work or one of its slices (`/enable`, or in words) — including small work that never cut slices, built against its confirmed problem. A work whose `next:` names this stage is not that ask, because the flow never advances itself.
2 files6stars - tenacitydonald-ada/workinggenius
Drive the work to actually-done — fresh verification of every claim, context-isolated diff review, cleanup, commit, post-mortem. Use when the user asks to close out a tracked piece of work (`/tenacity`, or in words), whether it moved through slices or was built directly after Wonder without them. A work whose `next:` names this stage, or whose last slice just closed, is not that ask, because the flow never advances itself.
2 files6stars - compactdonald-ada/workinggenius
Put the compaction question to a snapshot that drifted — route what no longer constrains unfinished work, and say what moves before moving it. In flight or done; the log is appended to, never edited or trimmed.
6stars - geniusdonald-ada/workinggenius
The map of the Working Genius workflow — where each piece of work stands, what to run next, and where genius gaps are hiding.
6stars - reconciledonald-ada/workinggenius
Check the project's binding documents against the repo they describe — settled decisions, glossary terms, pinned commands, in-flight plan contracts, the links between file and record — and route every drift to its correction.
6stars - designerdonald-ada/workinggenius
Settle the look before the pixels — audience and context first, then the base and the delta, directions drawn as tiles from a written brief and a critic's read of the chosen one, accessibility as the floor, one design language committed to DESIGN.md as tokens with roles. A command the user types, for work with an interface someone will see; standalone, no other skill required.
15 files6stars - discerndonald-ada/workinggenius
Explore the paths first where none are on record (the `invent` skill), then attack every path adversarially with one blind attacker per path, commit to one, and present the commitment — consequences for the user to confirm, kills on the record. Use when the user asks to run discernment on a tracked piece of work (`/discern`, or in words), or asks for a ready-made plan to be attacked before it is built. A work whose `next:` names this stage is not that ask, because the flow never advances itself, and a plan handed over to be implemented is not an invitation to attack it or to start the flow.
2 files6stars - genius-filedonald-ada/workinggenius
Read and update Working Genius work files — the work's folder holding the bounded snapshot a cold session acts on, the append-only log behind it, and the contract that binds the unbuilt slices. Use when a stage skill needs the work-file discipline, when the user asks what work is in flight or where a piece of work left off, or before resuming any work tracked under .genius/.
6 files6stars - inventdonald-ada/workinggenius
Genuinely explore structurally different approaches before committing — the alternatives exist to be beaten, not to be presented. Runs as the first half of `/discern` when the work has no paths on record yet; used on its own when the user asks for invention alone on a tracked piece of work (`/invent`, or in words). A work whose `next:` names a stage is not that ask, because the flow never advances itself.
2 files6stars - architectdonald-ada/workinggenius
Answer build-or-adopt honestly, then design one committed architecture from your own understanding of the problem — driven by ranked quality attributes, stress-tested against the field and against change, proven by a walking skeleton, its consequences confirmed by the user, committed to ARCHITECTURE.md. A command the user types, for greenfield or architecture-shaping work; standalone, no other skill required.
6stars - attackdonald-ada/workinggenius
Put a plan, a design or a set of approaches the user hands over under blind attack, one attacker per path, and report what broke each and what each survived. User-invoked only, and outside the flow, so nothing is tracked and no work file is written.
6stars - blindspotdonald-ada/workinggenius
Find the unknowns before they find the work — a read-only territory pass that surfaces the questions nobody knew to ask, judgment taught before a choice is extracted, and a quiz that catches the user's map up with what actually changed. Use when work enters territory the user calls unfamiliar, when the user is confirming a choice they can't evaluate, or when the user asks what they're missing or wants to be quizzed before accepting built work.
6stars - decision-recorddonald-ada/workinggenius
Keep the index of the project's settled decisions in .genius/DECIDED.md — one line per decision, pointing at the fight that settled it, earned by one test: would a future stranger re-fight this? Use when such a decision lands, when a design might contradict a settled one, or when another skill needs the index discipline.
6stars - diagnosedonald-ada/workinggenius
Debugging as the six geniuses at minute scale — the bug confirmed by a red reproduction before any theory, hypotheses plural with kill-reasons before any fix, the fix proven by a fresh green rerun. Use when something is broken, throwing, failing, flaky, or slow, or when the user asks to debug or diagnose.
6stars - domain-glossarydonald-ada/workinggenius
Maintain the project's shared vocabulary in CONTEXT.md — challenge conflicting terms, sharpen fuzzy language, record resolutions inline. Use when a term being settled with the user conflicts with the glossary or means two things, when a decision names a new project concept that later work will need a word for, or when another skill needs the glossary discipline. Reading CONTEXT.md to use its vocabulary is not this skill, and an ordinary request that uses a term is not an invitation to start a glossary.
6stars - erratadonald-ada/workinggenius
Correct what was written wrong — the binding line rewritten in place, the record it came from appended to and never touched, both carrying the evidence that overturned it. Use when a run, a file, or the user contradicts something already written in a work file, a plan's contract, the glossary, or the decision index; when a pinned value or a stated fact turns out not to hold; or when another skill needs the correction discipline.
6stars - fresh-eyesdonald-ada/workinggenius
Have a diff reviewed by a reviewer with no memory of how it was written, judged against what the user says it should do, and report what it would block on with evidence. User-invoked only, and outside the flow, so nothing is tracked and no work file is written.
6stars - galvanizedonald-ada/workinggenius
Turn the chosen design into mobilized work — a brief, vertical slices with acceptance criteria, and agreed test seams. Use when the user asks to run galvanizing on a tracked piece of work (`/galvanize`, or in words). A work whose `next:` names this stage is not that ask, because the flow never advances itself.
6stars - record-prosedonald-ada/workinggenius
How the flow's records are written — every document under .genius/, snapshot to backlog line. Use when writing or rewriting any of them, or when another skill needs the prose discipline.
6stars - setup-working-geniusdonald-ada/workinggenius
Per-repo configuration — pin the work-file directory, verify commands, and issue tracking, seed the project docs, and leave the pointer that tells every future session this project works this way.
6stars - triagedonald-ada/workinggenius
Put the backlog's own rules to the backlog — seeds that should no longer be there, pairs that are one discovery, seeds that outgrew a line, and the order nobody has stated. Judged one at a time, landed only by the user's call.
6stars - wonderdonald-ada/workinggenius
Question the work before doing it — the interview that turns a raw idea into a confirmed problem statement. Use when the user asks to run the interview on a tracked piece of work (`/wonder`, or in words), or when the user asks to start the Working Genius flow — or to be questioned — on a new idea. An ordinary request to build something is not an invitation to start the flow.
6stars - waitwhatdonald-ada/workinggenius
Explain what was just said, and why it is being done this way, in plain everyday words a newcomer can follow — the problem it solves, what goes wrong without it, what was given up. User-invoked only; only the reader knows when understanding broke.
6stars
workinggenius plugin questions
How do I install the workinggenius plugin?
In Claude Code run /plugin marketplace add donald-ada/workinggenius, then /plugin install workinggenius@workinggenius.
What does the workinggenius plugin include?
workinggenius bundles 23 skills.
How do I update or remove the workinggenius plugin?
Update it with claude plugin update workinggenius@workinggenius in your shell, or from the Installed tab of /plugin. Remove it with /plugin uninstall workinggenius@workinggenius.
What license is the workinggenius plugin under?
MIT, as stated in the plugin's manifest.