Results for “pr”

Guides users in setting product or service prices using minimalist entrepreneur principles, covering cost-based and value-based models, tiered pricing, and financial independence math.

Turn a product idea into a manual-first process you can start delivering today, before writing any code.

Guides strategic product decisions, pricing, backlog prioritization, and trend intelligence, routing tasks to specialized sub-skills.

Validates product direction before building, runs product diagnostics, founder reviews, user journey audits, and feature prioritization, producing actionable briefs and recommendations.

Create a comprehensive Product Requirements Document using an 8-section template covering problem, objectives, segments, value propositions, solution, and release planning.

Structure spoken product-sense interview answers with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs.

Design value-based pricing, packaging, and monetization strategies for SaaS products, including tier structures, value metrics, and price optimization.

Trigger: PRD, product requirements, spec, problem framing, project scoping, roadmap. Scope: Creating and updating product requirement documents and framing problem scopes. Boundary: Excludes code implementation, design mocks, or CI/CD config.

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Gated PRD generation — interrogates problem, user, and metric before drafting; refuses to draft on unknowns. Usage: /prd <feature-or-problem>

Design pricing strategies grounded in value delivery, competitive positioning, and willingness to pay. Recommends pricing models, tiers, and experiments.

Define a lightweight, disposable Proof of Life probe to test a risky hypothesis cheaply and surface harsh truths before building real product.

Trigger: press release, PM memo, PRD memo, product launch narrative, launch story. Scope: Writing press releases and future launch stories for project alignment. Boundary: Excludes writing functional code or task tracking.

Guide product managers through structured PRD creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document.

Creates an approval-gated product requirements document or decomposes an approved PRD into a traceable roadmap, covering product-level problems, new initiatives, multi-feature scope, PRDs, release outcomes, and roadmap planning.

Gated PRD generation — interrogates problem, user, and metric before drafting; refuses to draft on unknowns. Usage: /prd <feature-or-problem>

Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy.

Moves issues and external PRs through a state machine of triage roles, categorizing, verifying, grilling, and writing agent-ready briefs.

Provides professional, employee-centered HR guidance and templates for hiring, onboarding, PTO, performance management, employee relations, and offboarding, with a strong emphasis on compliance and legal disclaimers.

Creates and manages Product Requirements Documents (PRDs) with structured user stories, acceptance criteria, and progress tracking for feature planning.

PRD Writer

Trigger: PM, product tasks, project planning, backlog priority, user stories, ticket scoping. Scope: Product management, task priorities, requirements scoping. Boundary: Excludes writing raw code or designing page layouts.

Drafts stipulated ESI protocols for federal e-discovery. Produces court-ready agreements governing preservation, collection, processing, review, and production of electronically stored information under FRCP Rules 26, 34, 37 and Sedona Principles. Trigger when formalizing ESI procedures between parties during the discovery phase.

This skill should be used when the user asks to "create PRD", "write product requirements document", or mentions "PRD", "product requirements document".

Guide product managers through a complete discovery cycle from problem hypothesis to validated solution using problem framing, customer interviews, synthesis, and experimentation.

Validates product direction through structured diagnostics, founder reviews, user journey audits, and feature prioritization before building.

Extract structured product launch data from Product Hunt leaderboards, enriched with maker profiles and website contact information.

Prd

Write a Product Soul document — the strategic north star that sits above any PRD or feature spec. Captures the product's reason for existing across five lenses: user, business, strategy, product-market fit, and GTM distribution. Load when the user asks to write a product soul, product strategy doc, product north star, product positioning doc, product one-pager, or "why we exist" document. Also triggers on "write the soul of this product", "product strategy document", "what is this product really about", "capture the product vision", or when an agent needs strategic context before making product decisions. The output is docs/product-soul.md — a living document that brainstorming, prd-writing, and inversion can reference for grounding.