requirements-gatherer

A Claude Code plugin marketplace for product design, project planning, and testing workflows.

Plugins

requirements-gatherer

A senior product consultant that interviews you to understand what you want to build, then produces a structured requirements.md file. It defines WHAT and WHY, never HOW — no architecture, no tech recommendations, no implementation details.

Supports two modes:

New mode — when no requirements.md exists, runs a full requirements interview from scratch.

Addendum mode — when requirements.md already exists, reads it first, then interviews you about what's new or changing. Produces a separate requirements-addendum-[date].md file. The original is never modified.

Trigger phrases:

New: "gather requirements", "requirements interview", "what should we build", "help me define the requirements", "I want to build [something]"
Addendum: "add requirements", "update requirements", "I want to add a feature", "add to requirements"

What it does:

Asks 1-2 questions at a time, pushes back on vagueness, names patterns
Silently researches your domain to ask informed questions
Proactively surfaces gaps you haven't considered
Challenges scope creep and helps find the MVP
In addendum mode, flags contradictions with existing requirements and traces ripple effects
Produces a structured document after a narrative playback and confirmation step

requirements-organizer

Reads a reviewed requirements.md or requirements-addendum-*.md and creates structured epics and issues in GitHub or Jira. You trigger this after reviewing and editing the requirements document.

Supports two modes:

Full mode — reads requirements.md, groups features into dependency-ordered epics, creates milestones, labels, and issues from scratch.

Addendum mode — reads a requirements-addendum-*.md file, fetches existing milestones and issues, then creates only what's new or changed:

New features become new issues in existing milestones (or new milestones if needed)
Modified features create a new issue that supersedes the old one (old issue is closed with a link to the replacement)
New open questions become separate needs-decision issues
Existing milestones and labels are reused, not duplicated

Trigger phrases: "create issues from requirements", "organize into epics", "push to GitHub", "push to Jira", "create tickets"

What it does:

Groups features into dependency-ordered epics (Epic 1 is always Foundations)
Presents the epic structure for your approval before creating anything
Creates milestones + issues (GitHub) or epics + stories (Jira)
Falls back to a backlog.md file if no GitHub/Jira integration is available
Open questions become needs-decision-labeled issues
Verifies everything was created correctly before reporting the summary

visual-design

visual-design-consultant

Establishes a project's visual design system through plain-language interview or by extracting patterns from example websites. Produces design-guidelines.md (core tokens, permanently in CLAUDE.md context) and a component compendium (design/components/) with detailed per-component specs.

Trigger phrases: "design system", "visual design", "extract design from [site]", "I want it to look like [site]", "design guidelines"

What it does:

Extracts design patterns from example sites (sitemap via WebFetch, CSS extraction + screenshots via Chrome, multi-site conflict resolution)
Interviews in plain language — no design expertise needed
Produces compact design-guidelines.md (under 500 lines) for permanent context
Generates per-component spec files in design/components/
Supports addendum mode to update existing design systems

component-context (skill + `visual-design:component-context` agent)

Off-thread lookup with three behaviors: (1) exact or high-confidence (~90%) fuzzy → the entire matched component spec file (full markdown) + motion guidance, no long briefing; (2) ambiguous fuzzy → auto top 3 full specs + pattern synthesis + motion; (3) no match → inferred guidance + motion from guidelines. Further candidates stay one-line only — never the whole compendium.

Trigger phrases: see the skill description in the plugin (e.g. "load component spec", "which component should I use", "no spec for", "map this UI to components"). Prefer dispatching the agent when implementing so the main session stays lean.

design-reviewer

Senior creative director quality gate. Verifies implemented UI against the design system through chrome-devtools-mcp (live browser inspection): visual appearance, CSS/token compliance, accessibility (axe), motion, responsive behavior, and Nielsen’s 10 usability heuristics with a 0–100 UX score. Supports diff mode (compare to a prior design-review-*.md report) and can consume design/review-checklist.md from the consultant.