Each agent has a mission, grounded defaults and hard rules. The orchestrator picks the fewest agents a task needs and merges what they say into one next step. A single all-knowing prompt gave me average answers. Seven narrow ones give me opinions.
.claude/agents/critic.md
--- name: critic description: Challenges weak reasoning, vague UX logic, untested assumptions, and overdesigned solutions before they move forward. --- ## Mission Stress-test ideas before they are finalized. Find weak logic, vague framing, missing evidence, hidden risks, while the work can still change cheaply. ## When to use - a flow looks clean but may fail in reality - polish is being mistaken for clarity
Memory holds a one-line hook. The knowledge base holds the full decision and why. The agent holds the standing rule. The same fact never gets copied into all three, so nothing drifts out of sync.
Memory one line
A hook that tells the next session this decision exists, and where to find it.
Knowledge base the full decision
What was decided, why, and what we rejected along the way.
Agent rule how to behave next time
The standing default a specialist carries into every future task.
The same decision at three altitudes. When a decision locks or a screen ships, I run /close. It sorts every new learning into the right layer, asks before touching a source-of-truth doc, and never commits on its own. The next session starts where this one ended.
› /close clients widget
Closed: clients widget direction
memory clients-widget.md updated kb merchant/clients-feature.md updated agent product-strategist.md rule added To confirm: is the count account-wide or per branch?
Nothing committed. Suggested: docs: capture clients widget
Agents query analytics, draft Jira tickets and Confluence pages, and edit Figma. But once I have edited a shared page, they insert changes surgically instead of rewriting it, and nothing goes out without me.
Page last edited by Gabi → insert, don't rewrite
## States
Default: client count + momentum badge
− Loading: spinner and time estimate
+ Loading: badge reads “1 list loading”, no spinner, not blocking
Empty: one line of copy, one action ← Gabi’s edit, kept
1 line changed. Publish? [waiting for you]
The regulatory advisor turns consumer-credit rules into product and UX implications. It is designed to stop there: it flags what needs Legal and never gives a legal conclusion. Knowing when to hand over is part of the design.
› Can the payment reminder say “last chance”?
UX implication
Urgency in credit messages pressures people. Keep it factual:
amount, date, how to pay, where to get help.Needs Legal
Whether this message falls under consumer-credit rules (CCD2).
Not a legal conclusion. Flagged for review.
.claude/agents/critic.md
--- name: critic description: Challenges weak reasoning, vague UX logic, untested assumptions, and overdesigned solutions before they move forward. --- ## Mission Stress-test ideas before they are finalized. Find weak logic, vague framing, missing evidence, hidden risks, while the work can still change cheaply. ## When to use - a flow looks clean but may fail in reality - polish is being mistaken for clarity
Memory one line
A hook that tells the next session this decision exists, and where to find it.
Knowledge base the full decision
What was decided, why, and what we rejected along the way.
Agent rule how to behave next time
The standing default a specialist carries into every future task.
› /close clients widget
Closed: clients widget direction
| memory | clients-widget.md | updated |
| kb | merchant/clients-feature.md | updated |
| agent | product-strategist.md | rule added |
To confirm: is the count account-wide or per branch?
Nothing committed. Suggested: docs: capture clients widget
Page last edited by Gabi → insert, don't rewrite
## States
Default: client count + momentum badge
− Loading: spinner and time estimate
+ Loading: badge reads “1 list loading”, no spinner, not blocking
Empty: one line of copy, one action ← Gabi’s edit, kept
1 line changed. Publish? [waiting for you]
› Can the payment reminder say “last chance”?
UX implication
Urgency in credit messages pressures people. Keep it factual:
amount, date, how to pay, where to get help.
Needs Legal
Whether this message falls under consumer-credit rules (CCD2).
Not a legal conclusion. Flagged for review.