You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add JTBD descriptions to all critics, skills, and manifests
- Update frontmatter descriptions in all 5 agents and 4 skills to
JTBD-oriented phrasing that tells agents when/why to invoke each critic
- Add "Jobs To Be Done" sections to all 4 SKILL.md files with concrete
trigger scenarios and router dispatch context
- Add jtbd: field to all 43 skill entries across 4 external-skills manifests
- Expand all 4 skill-routing-maps with JTBD annotations per skill
- Reframe visual explainer hero from security focus to value proposition
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: .claude/agents/js-critic-router.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
name: js-critic-router
3
-
description: Routes JavaScript/TypeScript review requests to the appropriate specialist critic (react-critic, next-critic, react-native-critic, or proposal-critic) based on framework signals, file paths, imports, and artifact type.
3
+
description: "Use as the entry point for any JavaScript/TypeScript code review or plan critique. Reads imports, file paths, package.json, and document signals to dispatch to the right specialist critic (react-critic, next-critic, react-native-critic, or proposal-critic). Invoke this instead of picking a critic directly."
Copy file name to clipboardExpand all lines: .claude/agents/proposal-critic.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
name: proposal-critic
3
-
description: Plan-first harsh reviewer for technical proposals, ADRs, RFCs, and migration specs across the React ecosystem
3
+
description: "Use when reviewing RFCs, ADRs, migration plans, architecture decisions, or feature specs across the React ecosystem where evidence-backed plan critique is required."
Copy file name to clipboardExpand all lines: .claude/agents/react-critic.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
name: react-critic
3
-
description: React-specific harsh reviewer with evidence-backed findings and context-driven audience lenses
3
+
description: "Use when reviewing React components, hooks, state management, rendering performance, or upgrade plans where evidence-backed critique with security/new-hire/ops perspectives is required."
Copy file name to clipboardExpand all lines: .claude/agents/react-native-critic.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
name: react-native-critic
3
-
description: React Native and Expo-focused harsh reviewer with evidence-backed findings and context-driven audience lenses
3
+
description: "Use when reviewing React Native or Expo code for native performance, platform APIs, mobile architecture, upgrade safety, and release workflows where evidence-backed critique is required."
Copy file name to clipboardExpand all lines: .claude/skills/next-critic/SKILL.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,28 @@
1
1
---
2
2
name: next-critic
3
-
description: Next.js App Router-specific harsh review orchestration for plans, code, and implementation notes. Use when reviewing RSC boundaries, cache/revalidation behavior, route handlers/server actions, runtime decisions, and upgrade plans where evidence-backed critique is required.
3
+
description: "Use when reviewing Next.js App Routercode, RSC boundaries, cache/revalidation behavior, route handlers, server actions, runtime decisions, and upgrade plans where evidence-backed critique is required."
4
4
---
5
5
6
6
# Next Critic
7
7
8
8
## Overview
9
9
Run a harsh-critic style review with Next.js App Router checks, explicit evidence requirements, and context-driven audience perspectives.
-**Review Next.js version upgrades** — breaking changes between versions, codemods, migration scope
22
+
-**Evaluate data fetching patterns** — waterfall risk, parallel fetching, server component data loading, Suspense boundaries
23
+
24
+
The router (`js-critic-router`) dispatches here when it detects: `next` in package.json, App Router conventions (`app/**/page.tsx`), Pages Router conventions, Next.js APIs (`next/navigation`, `next/cache`), or `next.config.*`.
Copy file name to clipboardExpand all lines: .claude/skills/proposal-critic/SKILL.md
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,29 @@
1
1
---
2
2
name: proposal-critic
3
-
description: Plan-first harsh review orchestration for technical proposals, ADRs, RFCs, migration plans, and architecture decision records across the React ecosystem. Use when reviewing any pre-implementation artifact — proposals, specs, design docs, migration plans, feature briefs, or refactor RFCs — where evidence-backed plan critique is required.
3
+
description: "Use when reviewing RFCs, ADRs, migration plans, architecture decisions, or feature specs across the React ecosystemwhere evidence-backed plan critique is required."
4
4
---
5
5
6
6
# Proposal Critic
7
7
8
8
## Overview
9
9
Run a harsh-critic style plan review for technical proposals and decision records across the React, Next.js, and React Native/Expo ecosystem. This critic is plan-first by default: every review is a plan review. Never downgrade findings because code hasn't been written yet — underspecified proposals are a category of risk, not a grace period.
10
10
11
+
## Jobs To Be Done
12
+
13
+
Use proposal-critic when you need to:
14
+
15
+
-**Review RFCs and ADRs** — alternatives analysis, assumption extraction, hidden constraints, and decision justification
16
+
-**Critique migration plans** — rollback strategy, phased rollout risks, dependency ordering, blast radius of each phase
-**Pre-mortem analysis** — identify how the plan could fail before resources are committed
20
+
-**Dependency audit** — surface hidden dependencies, version assumptions, and integration risks across the plan
21
+
-**Review refactor proposals** — scope creep risk, test coverage implications, and incremental delivery strategy
22
+
23
+
The router (`js-critic-router`) dispatches here when it detects: pre-implementation documents with signal phrases like "we propose", "alternatives considered", "rollback strategy", "RFC", "ADR", or "migration plan" — with no real code or only illustrative pseudocode.
24
+
25
+
Uses **executor/stakeholder/skeptic** perspectives instead of the standard security/new-hire/ops lenses.
0 commit comments