claude-plugins/composer/commands/composer-review.md at 0cdbb1b4a403d979c0c0c4a6fe46841a58ee8a4b

Files

movq 594fccc80a feat(composer): discovery-phase plugin from "I want an app that..." to tracker-loaded stories

Plugin pairs with Symphony — Composer's output (issues in the project's
tracker) is Symphony's input. State-aware /composer command walks the
user through 11 phases: concept, users (with workflow probing for hidden
actors), requirements/NFR/IA, design system, interaction design, flows,
mocks, architecture, stories, roadmap, load. Each phase produces a
reviewable artifact in docs/planning/ (or, for design and interaction,
a project-local skill — see below).

Architecture is intentionally LAST, after the spec is complete. Mocks
are JSX/TSX regardless of final stack and pass a "text feasibility"
audit — every visible string is categorized (static/computed/authored),
computed strings are traced to source data, and any string implying an
unspecified feature halts the commit.

Design system and interaction design are produced as PROJECT-LOCAL
SKILLS in .claude/skills/<slug>-design-system/ and
.claude/skills/<slug>-interaction-design/, not as docs in
docs/planning/. Skills auto-load via description matching whenever UI
work happens; a reference doc gets read once and drifts out of context.
The mocks skill imports tokens directly from the design-system skill
for a single source of truth across mocks and (eventually) real code.

ui-system is currently a PLACEHOLDER — captures the minimum needed for
mocks to proceed with <TBD: ...> markers as a return-pass worklist.
Full interview specification is the next pass.

Council touchpoints baked in: PM/skeptic/end-user after requirements,
end-user/a11y after mocks, full architecture council after architecture,
plus auto-additions (legal-triage on regulated data, privacy-advocate
on PII, finance-controller on money flows).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-29 21:03:40 -05:00

1.4 KiB

Raw Blame History

description, arguments

description

arguments

Summon a Council of Experts to review the current planning artifact. Defaults to a phase-appropriate council; accepts an explicit council list. Use when you want a stress-test of what you've drafted before moving on.

name	description	required
artifact	Optional artifact name (e.g. "scope", "requirements", "architecture", "log-feeding"). Defaults to whatever Composer thinks the current phase is.	false

name	description	required
council	Optional explicit comma-separated council member names (e.g. "Vera,Lena,Femi"). Overrides the phase default.	false

Invoke the composer skill in review mode with $ARGUMENTS.

The skill will:

Identify which artifact to review — the one named, or the current phase's artifact.
Pick a council. Defaults from the phase boundary (see CLAUDE.md); user override accepted. Composer also auto-adds members when content suggests their domain (PII → Camila, money → Ingrid, regulated data flows → Femi).
Read the artifact and any upstream context the council needs.
Hand off to the council-of-experts:council skill with the question framed for the artifact under review.
Record the synthesis and suggested takeaways in docs/planning/reviews/<artifact>-<date>.md so future phases see prior feedback.

The output is the council's standard format: each member in their own voice, then agreements, disagreements, and prioritized takeaways.

1.4 KiB Raw Blame History

1.4 KiB

Raw Blame History