Product & Planning

ericrisco Bundle

Use when starting from nothing or pointing rsc at an existing project — the front door. Gauges technical level and the accompaniment dial first (non-technical by default), discovers what the user wants to build or govern (any stack, or a non-code harness: company/ops, research, knowledge, content), writes the profile to 02-DOCS, and installs the skills discovery justified. NOT the scaffolder (that is `harness`), NOT a stack skill.

ericrisco Bundle

Use when writing the document a buyer reads to say yes — a commercial proposal or Statement of Work, turning discovery notes into a scoped and priced document, adding tiers so the middle one wins, or diagnosing a proposal that will not close. NOT the binding legal agreement with its liability and IP clauses (that is `contracts`), NOT deciding the number or the margin (that is `pricing`), NOT the deck that pitches the vision to a room (that is `pitch-deck`).

lukasa1993 Bundle

Isomorphic tool system: toolDefinition() with Zod schemas, .server() and .client() implementations, passing tools to both chat() on server and useChat/clientTools on client, tool approval flows with needsApproval and bound interrupts (resolveInterrupt), generic middleware interrupts with defineInterrupt(), lazy tool discovery with lazy:true, rendering ToolCallPart and ToolResultPart in UI.

lukasa1993 Bundle

Retrieve machine-readable context with tanstack libraries, tanstack doc, tanstack search-docs, tanstack create --list-add-ons --json, and --addon-details for agent-safe discovery and preflight validation.

contextgo Skill

Turn discovery context into a clear PRD with problem framing, scope boundaries, requirements, and success criteria.

contextgo Skill

Build product strategy by connecting market context, target customer, strategic choices, and roadmap direction.

contextgo Skill

Build an outcome-driven roadmap by defining initiatives, sequencing them, and communicating confidence and tradeoffs.

contextgo Skill

Run evidence-led product discovery from outcome framing to interviews, synthesis, and experiments before commitment.

contextgo Skill

Draft a polished office memo or report that stays concise, traceable, and ready for real stakeholder review.

contextgo Skill

Choose and apply the right prioritization lens for the current product stage, evidence quality, and stakeholder environment.

contextgo Skill

Build an outcome-to-opportunity map before converging on solutions or roadmap commitments.

contextgo Skill

Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".

shengdabai Skill

Discover patterns, rules, and interfaces through iterative analysis cycles. Use when analyzing business rules, technical patterns, security, performance, integration points, or domain-specific areas. Includes cycle pattern for discovery to documentation to review workflow.

shengdabai Bundle

Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on product-requirements.md files in docs/specs/. Includes validation checklist, iterative cycle pattern, and multi-angle review process.

shengdabai Bundle

Initialize and manage specification directories with auto-incrementing IDs. Use when creating new specs, checking spec status, tracking user decisions, or managing the docs/specs/ directory structure. Maintains README.md in each spec to record decisions (e.g., PRD skipped), context, and progress. Orchestrates the specification workflow across PRD, SDD, and PLAN phases.

shengdabai Skill

Validate implementation against specifications (PRD/SDD/PLAN). Use when verifying specification compliance, checking interface contracts, validating architecture decisions, detecting deviations, or ensuring implementations match documented requirements. Provides structured compliance reporting.

allinherog-star Bundle

业务诊断助手适合technical、管理者、software、PRD在用户提出“这件事该怎么做”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。

pooriaarab Skill

Use when you are showing how something is put together: architecture posts, product teardowns, system diagrams, a roadmap that must look thought through rather than dreamt up. Applies the blueprint direction to every surface, not only the website. Triggers: 'blueprint direction', 'drafting sheet', 'dimension lines', 'architecture post', 'product teardown', 'technical drawing look', 'annotate the design'.

pooriaarab Skill

Build, publish, and get the verified badge for an n8n community node (the code under integrations/n8n/ — nodes/ + credentials/). Use when creating an n8n node, publishing it to npm so it's installable, debugging why n8n doesn't recognize the package, or submitting for the verified badge via the Creator Portal. Covers the three package.json fields that gate discovery (n8n-nodes- name, the community-node keyword, the n8n object with compiled dist/ paths), the npm-publish auth gotchas (automation token / 2FA / --ignore-scripts), the declarative credential authenticate block that centralizes auth, and the verified-badge hard cutoffs (npm provenance from 2026-05-01, zero runtime deps, the scanner, English-only). Sibling of connector-directory-submission (the cross-platform router) and zapier-integration. Verified 2026-08.

pooriaarab Skill

Use when a product idea has no code and someone asks to 'validate an idea', 'talk to customers before building', 'run customer discovery', 'do problem interviews', 'test demand', 'run a fake-door test', 'build a waitlist', or asks 'should we build this?'. Use before `name-a-product` or `build-from-template` when the idea still needs evidence that a specific customer has a painful, current problem.

pooriaarab Skill

Plan or run the first founder-led sales motion for a new SaaS or software product: build a named prospect list, write cold outbound, prepare discovery calls and demos, handle objections, track a manual pipeline, or move qualified buyers to self-serve. Use when the user asks for 'founder-led sales', 'cold outreach', 'cold email', 'book demos', 'sales calls', 'talk to prospects', 'find design partners', 'build a prospect list', or 'set up a sales pipeline' for an early product. Skip paid-ad setup, lifecycle email infrastructure, and CRM implementation unless the request includes the founder sales motion.

pooriaarab Skill

Use when the product ships automation-platform connectors or agent plugins — an n8n community node, a Make (Integromat) app, Pipedream components, a Zapier integration, a Claude Code plugin, or a ChatGPT/Codex Apps-SDK app — and you want them listed on the public directories/marketplaces (n8n verified nodes, Make apps directory, Pipedream registry, Zapier app directory, a Claude Code plugin marketplace repo, the ChatGPT Plugins Directory). Sibling of mcp-directory-submission (that one is MCP servers only). Covers which destinations index a plain npm package (n8n, npm auto), which are a PR into a vendor monorepo (Pipedream), which are a dev-portal review with a partner/active-user gate (Make, Zapier, ChatGPT), and which are just a git repo users add (Claude Code plugins). Per platform: the exact package.json/manifest field that gates discovery (n8n keyword + n8n object, Pipedream component key, plugin.json/marketplace.json), the real submission entry point (npm index, developers.make.com review form, Pipedream

samarv Bundle

Build and maintain Opportunity Solution Trees - visual artifacts that map outcomes to opportunities to solutions to assumption tests. Use when creating a new OST, updating an existing tree, validating tree structure, or organizing discovery work. The OST is a living document that evolves as teams conduct interviews and run experiments. Triggers when user asks to "create an OST", "build opportunity solution tree", "update the tree", or "organize our opportunities".

samarv Skill

Drafts concise, professional PM emails using the CRAFT method. Use when user needs to compose, draft, write, or rewrite professional email communication including follow-ups, status updates, escalations, and stakeholder messages.

samarv Bundle

Frame customer opportunities as unmet needs, pain points, and desires rather than solutions. Use when writing opportunities for an Opportunity Solution Tree, validating opportunity statements, or training teams to distinguish problems from solutions. CRITICAL for avoiding the

samarv Skill

A three-step framework (Articulate, Ask, Accept) to overcome career stagnation and interpersonal conflict by expressing needs with integrity. Use this when you feel stuck in your career, are avoiding a difficult conversation with a stakeholder, or need to align a team on a high-stakes deadline.

samarv Skill

A framework to align product team activities with business-critical outcomes. Use this when setting quarterly goals, justifying team headcount to leadership, or prioritizing a backlog to avoid the "low-impact death spiral."

samarv Skill

Apply product management rigor to professional growth by creating a "Career Spec." Use this when you feel stagnant in your current role, are evaluating a competing job offer, or want to transition from accidental career drift to intentional leadership.

samarv Skill

A systematic, survey-based framework to measure and increase Product-Market Fit (PMF). Use this when a product launch feels stagnant, when determining which user feedback to prioritize, or when planning a roadmap to reach the "40% Very Disappointed" benchmark.

samarv Skill

A framework for aligning teams through outcome-oriented OKRs and a rigorous weekly execution cadence. Use this when a team is spreading themselves too thin (the "peanut butter" effect), lacks a clear definition of success for the quarter, or struggles with "boring" status meetings that focus on tasks rather than impact.

samarv Skill

Transition from date-driven Gantt charts to a problem-based roadmap that acknowledges uncertainty. Use this when stakeholders demand unrealistic deadlines, when long-term plans are frequently missed, or when your roadmap feels like a list of features rather than a strategy.

samarv Skill

A strategy for breaking organizational stagnation by identifying and challenging "untouchable" product constraints. Use this when your roadmap has become purely incremental, when the team is risk-averse, or when customers complain that the product hasn't changed in years.

samarv Skill

A framework to evaluate product hypotheses by balancing customer delight, competitive advantage (hard-to-copy), and business viability (margin-enhancing). Use it when vetting a major new feature, defining a long-term product roadmap, or deciding whether to kill an existing initiative.

samarv Skill

Categorize and balance your product roadmap using the "4 BB" framework to align leadership on strategic trade-offs between stability, optimization, and innovation. Use this during quarterly planning, when technical debt is accumulating, or when the team is struggling to balance moonshots with maintenance.

samarv Skill

Shift focus from AI hype (latest models, vector DBs, agentic frameworks) to high-leverage activities that actually improve product quality. Use this when an AI feature is underperforming, when the team is stuck in a "research loop," or when planning the roadmap for a new AI application.

samarv Skill

Drive extreme clarity in complex, cross-functional projects by establishing a single source of truth, shared vocabulary, and structured decision frameworks. Use this when launching high-stakes initiatives, resolving stakeholder misalignment, or taking over "gnarly" projects where information is fragmented.