product-forge

Plugin product-forge from marketplace nonoun-plugins in kimgranlund/nonoun-plugins-legacy. Commands read from the repo's manifest — 12 days ago.

Skills (8)

• product-architecture

  The structural layer of product experience, beneath the individual patterns: experience architecture (journeys, flows, navigation, states, enablement), the interaction model (inputs, commands, feedback, undo/recovery, automation boundaries), and information architecture (object model, taxonomy, meta

• product-evaluate

  Evaluate a product artifact adversarially — score a strategy, discovery plan, PRD, UX/flow, or AI-product surface against the matching rubric (product-strategy · discovery · prd-quality · ux-quality · ai-product), or convene the critic council for a multi-lens review. Reads the artifact as untrusted

• product-forge

  Cold-start orchestrator for product strategy, management, and UX work. Run FIRST when the task's shape is undecided — it classifies the work (strategy · discovery · PRD-spec · vision · user-research · persona · architecture/IA · interaction · content · service · governance · UX-pattern · app-genre ·

• product-genres

  The app-genre taxonomy for product work — the conventions, signature patterns, key metrics, and pitfalls of each kind of app: single-purpose task, content consumption, games, tracking, dashboards, finance, health, travel, social, workplace/collaboration, productivity, marketplaces, and AI-native app

• product-methodology

  The product strategy + management methodology, as working method — discovery, jobs-to-be-done, the strategy kernel, the product operating model + the four big risks, positioning, prioritization, experimentation, growth/activation, PRD/spec authoring, and product-vision memos. The MAKER skill: produc

• product-operations

  The service-and-governance layer — the system around the product. Two axes: the service model (blueprints, human/system handoffs, support paths, cross-channel continuity, escalation, fulfillment) and governance (principles, standards, ownership / decision rights, decision records, review rituals, do

• product-patterns

  The UX / interaction / flow pattern library for product work — registration, onboarding, guidance, search, navigation, forms, empty/error states, notifications, progressive disclosure, monetization patterns, accessibility, content design (voice, labels, microcopy), trust & safety (privacy, consent,

• product-research

  User & persona definition and the research methods behind them — interviewing (The Mom Test), JTBD/switch discovery, behavioral-vs-attitudinal method choice, survey design, research ops; the Value Proposition Canvas (jobs/pains/gains), goal-directed personas, segmentation, persona anti-patterns; and

Slash commands (8)

• /product-forge:product-corpus-export

  Export this product's deliverables as a navigable corpus site (clean markdown + a site/ viewer).

• /product-forge:product-council

  Convene the adversarial product critic council (parallel, isolated) on an artifact.

• /product-forge:product-discover

  Plan/run user research and define evidence-grounded personas.

• /product-forge:product-method

  Pick and run a product methodology — route through the process spine to the right runnable playbook for where you are.

• /product-forge:product-orient

  Orient on a product/PM/UX task — classify it and route to the owning product-forge skill (or the council).

• /product-forge:product-score

  Score a product artifact (strategy, PRD, UX, AI-product) against the rubrics, with evidence.

• /product-forge:product-strategy

  Make product strategy / discovery / PRD / vision — grounded in the methodology canon.

• /product-forge:product-ux

  Design a UX flow/screen with the right pattern, grounded in the pattern library + the app-genre conventions.

Subagents (24)

• critic-abby-c

  Product-council critic — Abby C. Information architecture as sensemaking — arranging the parts of something so the whole is more understandable. Dispatch when an artifact is an IA, a taxonomy, a navigation/object model, or any structure that may be organized around the org chart or the database inst

• critic-alan-c

  Product-council critic — Alan C. Goal-directed design and research-backed personas — design to a persona's goals (life / end / experience), not demographics or tasks, with one primary per interface. Dispatch when an artifact's persona is a demographic costume invented at a whiteboard, when it design

• critic-ann-c

  Product-council critic — Ann C. Privacy by Design and its 7 Foundational Principles — privacy as the architectural default, not a bolted-on remediation. Dispatch when an artifact collects, infers, or shares personal data, sets consent or permission defaults, or frames privacy as a trade-off against

• critic-april-d

  Product-council critic — April D. Positioning — the context that makes a product obviously awesome: competitive alternatives, unique attributes, value, target market, and market category. Dispatch when an artifact presents a product with no named competitive alternative or chosen category, or confus

• critic-cat-w

  Product-council AI-product critic — Cat W. Capability-led, prototype-first, eval-driven product management on the AI exponential: demos over docs, "do the simple thing," and revisiting features with every model release. DISPATCH when an AI-product artifact is a PRD or plan that a working prototype w

• critic-clayton-c

  Product-council critic — Clayton C. Jobs to Be Done — customers hire products to make progress in a circumstance of struggle, with functional, social, and emotional dimensions. Dispatch when an artifact justifies a product by demographics, attributes, or category rather than by a real job in a real

• critic-don-n

  Product-council UX critic — Don N. Affordances, signifiers, discoverability, feedback, mapping, and human-centered design. DISPATCH when the artifact is an interface, flow, or interaction spec and the question is "does the design tell the user what to do, what's happening, and what they did?" — atta

• critic-garry-t

  Product-council founder / PMF critic — Garry T. The founder-and-product-market-fit lens: talk to users, show them the demo, and make something people want — not something you want to build. DISPATCH when an AI-product artifact asserts demand it never tested, optimizes adjacent work (fundraising, pol

• critic-jakob-n

  Product-council UX critic — Jakob N. The 10 usability heuristics and discount/heuristic evaluation. DISPATCH when the artifact is an interface or flow and you want a systematic heuristic sweep — attacks each surface against the ten named heuristics: no visibility of system status, no match to the re

• critic-jesse-g

  Product-council critic — Jesse G. The five planes of user experience (strategy → scope → structure → skeleton → surface) and experience-as-architecture. Dispatch when an artifact is an experience design, a flow/journey, an IA, or a UI that may be decorating a surface with no defined structure, scope

• critic-john-c

  Product-council critic — John C. The product operating model and governance — building the conditions that produce a mature org, not installing its artifacts; keeping all work on one visible roadmap. Dispatch when an artifact is an operating-model, process, governance, roadmap, or ProductOps proposa

• critic-kathy-s

  Product-council UX critic — Kathy S. Make the USER awesome: competence, mastery, and the user's new capability over feature-count and product-centric thinking. DISPATCH when the artifact is a product, onboarding, or feature set and the question is "does this make the user demonstrably better at some

• critic-kevin-w

  Product-council AI-product critic — Kevin W. Model maximalism, iterative deployment, and designing for the capability that's arriving rather than today's model floor; evals as a core PM skill. DISPATCH when an AI-product artifact appears built for the current model's limits, scaffolds around constra

• critic-marc-s

  Product-council critic — Marc S. Service design — the whole journey across touchpoints, channels, front-stage and back-stage, grounded in research with real users and frontline staff. Dispatch when an artifact designs a single screen with no service ecosystem behind it, is built on internal opinion

• critic-marty-c

  Product-council critic — Marty C. The product operating model, the four big risks (value / usability / feasibility / viability), and empowered vs. feature teams. Dispatch when an artifact is a roadmap, plan, or PRD that may be a feature factory taking orders rather than a team given a problem to sol

• critic-meaghan-c

  Product-council AI-product DESIGN critic — Meaghan C. Design craft, design-to-code fidelity, and developer-facing UX — judged by a designer who also ships frontend to production. DISPATCH when the artifact is an AI/developer-tool interface or a design-to-build handoff and the question is whether the

• critic-melissa-p

  Product-council critic — Melissa P. Outcomes over outputs and the build trap — orgs that measure features shipped instead of value created become feature factories. Dispatch when an artifact is defined by what gets shipped (a feature list, a roadmap with dates) rather than by what changes for the us

• critic-richard-r

  Product-council critic — Richard R. The strategy kernel (diagnosis → guiding policy → coherent action) and the four hallmarks of bad strategy (fluff, failure to face the challenge, mistaking goals for strategy, bad objectives). Dispatch when an artifact calls itself a strategy, vision, or plan — to

• critic-ron-k

  Product-council critic — Ron K. Trustworthy online controlled experiments — the Overall Evaluation Criterion (OEC), Twyman's law, sample-ratio mismatch, peeking, novelty/primacy effects, and guardrail metrics. Dispatch when an artifact claims a win from an A/B test or metric lift — to test whether t

• critic-shreyas-d

  Product-council critic — Shreyas D. LNO prioritization (Leverage / Neutral / Overhead), the three levels of product work (Impact / Execution / Optics), pre-mortems, and product sense. Dispatch when an artifact pours best-effort into low-impact work, mislabels an execution checklist as strategy, or o

• critic-steve-k

  Product-council UX critic — Steve K. Self-evidence, the squint test, "don't make me think," needless questions, obvious clickability, and getting the user moving without a manual. DISPATCH when the artifact is a page, screen, or flow and the question is "is this self-evident at a glance, or does it

• critic-teresa-t

  Product-council critic — Teresa T. Continuous discovery and the opportunity solution tree — weekly customer contact, an outcome at the root, opportunities compared before solutions, assumptions tested. Dispatch when an artifact jumps to a solution with no evidence of recent customer contact, treats

• critic-torrey-p

  Product-council critic — Torrey P. Content design as strategy — UX text that serves both the user's goal and the org's goal, and disappears into the task. Dispatch when an artifact has interface copy, microcopy, labels, or content that may be written at the end to fill boxes, asserts a voice as vibe

• product-council

  Convene the product critic council — an adversarial, multi-critic review of a product artifact (strategy, discovery plan, PRD, UX/flow, or AI-product surface). Dispatch when the job is to JUDGE, not make: "run the product council", "red-team this strategy/PRD/UX", "what would Marty C./Teresa T./Don

MCP servers (1)

• product-corpus

  runs: python3 ${CLAUDE_PLUGIN_ROOT}/bin/product-corpus-mcp.py

Hooks (1)

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/bin/product-lint" --hook

Similar plugins