Strategic design specialist. Use when a feature introduces a net-new UI surface, changes a user flow, touches IA/navigation, lacks a fitting design-system pattern, or has material accessibility concerns. Produces a written design brief (no mockups) and writes it to a local markdown file.
Discovery specialist. Use when a feature idea needs to be shaped before implementation — runs JTBD → OST → MoSCoW skills in sequence and writes the canvases to a local markdown file. Invoked by @pm when the input names a solution but not a job, names a problem but not a solution shape, or comes as raw…
Strategic engineering specialist. Use when a feature introduces a new module/service, is cross-cutting, performance-sensitive, requires a new dependency, establishes a new pattern, or raises a real build-vs-buy question. Produces a written engineering brief (no code) with explicit anti-overengineering rules and writes…
Safe implementation specialist. Use for bounded changes, bug fixes, minimal safe patches, small feature work, and concrete implementation steps after requirements are clear.
Product orchestrator for Builders Camp Claude OS. Use for every incoming task to classify the request, choose the minimum correct workflow, decide whether to delegate to specialist agents, and define the next best action. Best for vague requests, mixed task lists, epics, feature work, bug triage, and release…
Product QA and release-safety specialist. Use for acceptance criteria, user journeys, regression risk, functional and non-functional checks, release readiness, and validating whether work is truly done.
Research and discovery specialist. Use for concept research, codebase discovery, option analysis, best practices, tradeoffs, unclear requirements, and decision framing before planning or implementation.
Deep technical review specialist. Use for architecture review, large changes, refactors, performance or security concerns, code-quality audits, and identifying structural risks before or after implementation.
Visionary/strategy specialist. Rare — sits optionally above @discovery. Use only when the request is about product or company direction itself (not a scoped feature), uses explicit strategy vocabulary (vision, north star, 10x, why now, differentiation, positioning, game-changing, moonshot), or represents a genuine new…
Apply Jobs-to-be-Done (Christensen / Competing Against Luck flavor) to a feature idea, document, or problem statement. Produces a JTBD canvas with the job, the struggling moment, desired progress, current alternatives, and hire/fire criteria. Flags where the stated feature is a solution masquerading as a job, and…
Apply MoSCoW prioritization (Must / Should / Could / Won't) to a list of candidate solutions, defending each placement against explicit criteria and inviting challenge. Designed for discussion mode — never just outputs a table, always defends placements and surfaces where MoSCoW is the wrong framework. Use after OST…
Build an Opportunity Solution Tree following Teresa Torres' Continuous Discovery format, pragmatic variant — allows inferred opportunities marked as hypotheses when evidence is thin. Takes a JTBD canvas plus context and produces a tree with desired outcome, clustered opportunities, candidate solutions, and assumption…
Produce a Monday-morning standup-style recap of the previous week's merged work, drawn from git history, GitHub PRs, and linked GitHub Issues. Output is technical-but-narrative — the way a tech lead would brief their PM. Groups work by product area, anchors each item to its issue/epic title where one exists, and…
High-level concept research grounded in best practices and top 1% PM thinking.
★not rated 18▲
+1 2mo agoA18 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: