willtsai/product-cabinet

Evaluate technical feasibility and architecture implications of a product proposal, including system boundaries, data flows, contracts, dependencies, migration, operations, security boundaries, and alternatives. Use when product work changes architecture or needs technical evidence before specification or planning.

Conduct independent governance review of a material product proposal using customer, strategy, financial, technology, execution, trust, and risk perspectives. Use for high-impact, expensive, difficult-to-reverse, regulated, externally consequential, or disputed decisions requiring challenge, conditions, dissent, or escalation.

Rewrite text in the Classic Style described by Steven Pinker in "The Sense of Style" (drawn from Thomas & Turner's "Clear and Simple as the Truth"). Strips AI writing artifacts (em-dashes, "not just X but Y", delve/leverage, rule-of-three padding, reflexive hedging) and rewrites prose as a clear window onto the world: concrete nouns, active verbs, a visible agent, no metadiscourse. Use when the user says "rewrite in classic style", "classic style this", "Pinker-ify", "de-AI this", "make this sound human", or asks to remove em-dashes and AI tells.

Build evidence-based understanding of target users, unmet needs, existing alternatives, demand, and product assumptions. Use for customer discovery, problem validation, persona refinement, interview planning or synthesis, competitive alternatives, and learning plans before product commitments.

Review APIs, SDKs, CLIs, integrations, extensions, samples, and documentation as end-to-end developer experiences, identifying adoption friction, inconsistency, unsafe defaults, missing guidance, and feedback gaps. Use for developer product reviews, API usability, onboarding, documentation, samples, migration, and developer launch readiness.

Convert approved product requirements and architecture into a sequenced, dependency-aware, testable delivery plan with vertical work items, ownership, risks, estimates or sizing assumptions, and release gates. Use when planning implementation, decomposing a feature, sequencing delivery, or assessing execution readiness.

Develop or review product positioning, audience segmentation, launch strategy, channels, pricing or packaging implications, enablement, operational readiness, adoption measurement, and post-launch learning. Use for go-to-market plans, launch plans, messaging, audience strategy, sales or partner enablement, and launch readiness.

Orchestrate product strategy and delivery work by framing the request, selecting the minimum sufficient Product Cabinet capabilities, delegating bounded assignments, reconciling evidence and tradeoffs, and owning the final recommendation. Use when a user asks Product Cabinet to define, plan, review, prioritize, launch, or make a material decision about a product.

Review product workflows and interfaces for usability, information architecture, interaction clarity, consistency, accessibility, responsive behavior, failure recovery, and alignment with user outcomes. Use for UX reviews, design critiques, flow specifications, wireframe or mockup assessment, and user-facing acceptance criteria.

Create or review a concise, user- and product-focused feature specification that strictly follows the supplied template. Describe user stories, journeys, and observable experiences without cabinet deliberations or implementation details. Use when defining a feature, writing a feature spec or PRD, clarifying scope, or assessing specification completeness.

Independently evaluate a product artifact, implementation, or release against explicit requirements and evidence, report prioritized findings, and issue a PASS, FAIL, or UNVERIFIED verdict. Use for specification reviews, plan reviews, implementation conformance, test evidence reviews, and release readiness gates.