ljucask
UserProduct thinking, wired into your coding agent. AI-native product development framework for Claude Code - 50 skills spanning discovery, validation, domain modeling, JIT feature delivery (FDD+SDD), a client discovery layer for commissioned builds, and a reconciliation-based Rebuild playbook for existing products.
Categories
Indexed Skills (45)
design-thinking
Synthesize Phase 2 discovery outputs through Design Thinking (Define + Ideate stages). Produces Problem Statement, POV, HMW questions, and Ideation synthesis. Run in Phase 3a as the first step - feeds directly into pm-hypotheses. Takes Phase 2 outputs as input - no new research.
jtbd-building
Generate a JTBD Analysis using Bob Moesta's Jobs-to-be-Done framework. Produces job stories, Forces Diagram, and switching logic. Run in Phase 2 (Track D) after pm-personas. Output feeds pm-problem-validation and design-thinking.
pm-business-case
Generate a Business Case. Phase 3b skill. Synthesizes market size, business model, and KPIs into financial projections and investment rationale. Requires pm-lean-canvas and pm-kpis.
pm-business-model
Generate a Business Model Canvas from Phase 2 discovery outputs and founder knowledge. Phase 3b skill - runs after Go/No-Go = GO and Problem Validation Summary. Produces the commercial logic of the product.
pm-business-rule-core
JIT helper - add a single High priority operational rule to domain/business_rules.md. For standard business logic that governs normal system behavior (matching, pricing, SLAs, fulfillment). May have exceptions or context-dependent variations. Use during pm-feature-design or standalone when operational logic needs to be formalized.
pm-business-rule-critical
JIT helper - add a single Critical priority rule (hard invariant) to domain/business_rules.md. For rules where violation causes financial loss, legal exposure, or irreversible system damage. No exceptions allowed. Use during pm-feature-design when a missing invariant is identified, or anytime a new hard constraint needs to be formalized.
pm-business-rule-governance
JIT helper - add a single Compliance or Policy rule to domain/business_rules.md. For GDPR, regulatory obligations, admin constraints, data handling policies, and UX behavioral rules. Use when pm-privacy-requirements or pm-domain-analysis surfaces a regulatory requirement that needs a BR-ID for referencing in Feature Cards.
pm-business-rules-library
Build the Business Rules Library and Decision Models Matrix - Live Registers 2 and 3 of 4 in the FDD+SDD framework. Centralizes all business rules with unique IDs (BR-XXX-001) and decision tables into /domain/business_rules.md and /domain/decision_models.md. Replaces the upfront monolithic BRD with two continuously-maintained registers. Phase 4-5 skill - initial draft at Phase 5, enriched JIT in Phase 6 per feature.
pm-comms-charter
Generate a Communication Charter and Meeting Rhythm for a product team. Use in Phase 1 to establish collaboration rules.
pm-decision-model
JIT helper - add a single decision table (TBL-[DOMAIN]-NN) to domain/decision_models.md. For multi-condition logic where several inputs combine to produce different outputs (pricing matrices, eligibility rules, risk scoring, discount tiers). The decision-models counterpart to the single-rule helpers (pm-business-rule-core/critical/governance). Use during pm-feature-design when a multi-condition decision surfaces, or standalone - without re-running the full pm-business-rules-library.
pm-discovery-interview
Prepare a session-specific agenda for a live discovery session with a client, sponsor, or their users. Reads what discovery has already covered (meetings, Track artifacts), finds the biggest remaining gaps, and compiles a targeted agenda from its built-in discovery question bank (two planes - commissioner + real users; three user populations; full technique library - all embedded, no external file needed). Use before every client discovery session in Phase 2. After the session, process notes with pm-meeting.
pm-discovery-report
Generate the client-facing Discovery Report - a narrative "here is what we heard, here is what we recommend" document for whoever commissioned the work. Incremental and re-runnable - update it after each discovery session, finalize it when Phase 2 converges. Companion to pm-problem-validation (which stays the internal Go/No-Go verdict); this is the version you hand to the client. Feeds pm-scope-brief.
pm-domain-analysis
Generate a Domain Analysis Report and Legal & Regulatory Requirements document from raw research inputs. Use in Phase 2 (Track B) after collecting industry and regulatory research.
pm-domain-model
Generate a Domain Model - domain boundaries, entity catalogue, relationships, and ERD diagrams. Optional Phase 4 higher-level companion to pm-entity-registry - gives the cross-domain ERD and boundary view above the operational entities.md register. Two-stage output - confirm entity catalogue before generating entity definitions.
pm-entity-registry
Build the Entity & State Registry - Live Register 1 of 4 in the FDD+SDD framework. Extracts business entities from PRD Business Capabilities, defines their states and transitions in Mermaid.js, and writes to /domain/entities.md. Phase 4 skill - runs after PRD is complete. This is the operational register; pm-domain-model is the optional higher-level companion (cross-domain ERD and domain boundaries) that sits above it.
pm-feature-card
Create and manage Feature Cards for individual features (FEAT-ID). In the FDD+SDD framework, Feature Cards are the atomic delivery unit - one card per feature, living in /features/cards/. Cards are created as stubs by pm-features-list, populated in Sections 1-3 by pm-feature-design (JIT), and completed in Section 4 after build. This skill manages the card lifecycle and can create cards manually when needed.
pm-feature-design
JIT Design by Feature - Phase 6 skill. Just-In-Time technical design for a single feature before it enters build. Enriches the 4 live registers with guard conditions and finalized rules, generates a Mermaid.js sequence diagram, writes Acceptance Criteria, and completes Feature Card Sections 1-3. Replaces upfront Feature-Set design documents with JIT per-feature design. Run once per feature, triggered by pm-stripe when the feature is next in its Stripe.
pm-feature-viability
Feature Viability Assessment for Feature Implementation playbook. Run before JIT design to confirm a feature is worth building, how to scope it minimally, and what success looks like before build starts. Explicitly skippable when the decision is already made. Produces KANO classification, MDP definition, and pre-defined success metrics.
pm-features-list
Generate the complete Features List in FDD format, organized by Domain > Feature Set (grouping label) > Feature. Runs Dependency Map, KANO Analysis, and Value vs. Complexity Matrix. Creates stub Feature Cards in /features/cards/ for each feature. After user approval, pushes features to Notion as the initial backlog. Output is the prioritized, dependency-mapped feature inventory and Live Register 4 ready for MVP scoping in pm-mvp-scope.
pm-glossary
Generate and maintain a project glossary - terms, abbreviations, entities, artifacts, and concepts used across the product lifecycle. Runs progressively throughout the project. Can be called at any time to add terms, review existing entries, or export the full glossary.
pm-kotler
Define the product at Kotler's Five Levels of Product. Phase 3b - first skill after Go/No-Go = GO. Maps each level to KANO classification as a forward reference for Phase 5 feature planning.
pm-kpis
Generate AARRR funnel metrics, North Star Metric, and OKRs. Phase 3b skill. Requires Lean Canvas. Produces the measurement framework for the product.
pm-lean-canvas
Generate a Lean Canvas. Phase 3b - one-page business model optimized for validation-stage products. Runs after Go/No-Go = GO. Replaces Business Model Canvas for Greenfield and Feature Implementation.
pm-market-analysis
Generate Market Size Analysis (TAM/SAM/SOM), Competitor Analysis, SWOT, and Market Timing Rationale from raw research inputs. Use in Phase 2 (Track C).
pm-meeting
Structured meeting notes, summary, and action items from raw notes or a transcript. Detects meeting type (Customer Discovery, Client/Requirements Discovery, Product Review, Planning/Grooming, Strategic Review, Standup/Retro, Partner/Vendor) and applies the correct summary template. Tags each action item with its destination (Notion Task, Feature Card, follow-up meeting, framework skill). Pushes to Notion Meetings DB with linked tasks. Run after any meeting where notes or a transcript exist.
pm-mvp-scope
Define MVP scope and delivery plan from the prioritized FDD Feature List. Makes the IN/POST-MVP/CUT decision per feature (recorded in the single `phase` field, never a separate `mvp` flag), assigns each feature to a Delivery Stripe. Updates feature_list.md and Feature Card frontmatter (phase + stripe). If features already carry a phase (Rebuild where roadmap split phases), reads it instead of re-deciding the cut and only assigns stripes. After user approval, updates Notion Feature entries with phase and stripe assignment. Phase 5 exit artifact. Required input for pm-stripe JIT cycle.
pm-onboarding
Generate a role-specific Onboarding Brief for a new team member. Reads the existing workspace and distills the right subset of artifacts for the role (Developer, PM, Designer, Stakeholder/Investor). Produces a single navigable brief with product context, settled decisions, where-things-live map, current delivery state, and who to talk to. Run when a new person joins the team. Skip if solo builder with no team.
pm-personas
Generate Customer Segments, Personas (with Empathy Map and as-is journey), and Early Adopter Profile from raw VOC data (interview transcripts, synthetic interviews, survey data, discovery meeting notes). Tracks provenance - real VOC vs. [CLIENT-ASSERTED] client claims vs. assumptions. In commissioned builds also covers staff/operator personas. Use in Phase 2 (Track D, Step 1) before running jtbd-building.
pm-pitch-deck
Generate a structured pitch deck content brief. Determines presentation type, audience, and style via questionnaire. Applies validated investor feedback guidelines (82 + 590 deck analyses) to every slide. Outputs slide-by-slide content spec ready for Gamma.
pm-prd
Two modes. (1) Product PRD - Phase 3b exit artifact synthesizing all Phase 2+3a+3b outputs. Saves to product/PRD_master.md. Frozen after creation. (2) Initiative PRD - Feature Implementation context, after Track B discovery for a large new domain. Leaner document focused on Business Capabilities for that domain only. Saves to initiatives/[slug]/prd.md.
pm-prioritize
Re-runnable prioritization engine for the feature backlog. Works at ANY point - after the feature list is created, after the MVP cut, or any time later when priorities shift. Takes flexible input - align to a roadmap, follow a directive you give ("X first", "revenue first"), apply a prioritization lens, or let the skill propose a basis with reasoning. Always reconciles with the dependency map (cannot rank a feature ahead of its blocker), is non-destructive (proposes, you confirm before it writes), and explains the rationale and trade-offs. The canonical prioritization logic that pm-features-list offers for the first-time scoring.
pm-privacy-requirements
Generate a PII Inventory, Privacy Requirements document, and GDPR Action Plan for Phase 4. Runs after Domain Model - maps personal data to entities, identifies processing purposes, and produces a concrete compliance action list before build starts.
pm-problem-validation
Generate a Problem Validation Summary by synthesizing all Phase 2 research outputs (Tech Feasibility, Domain Analysis, Market Analysis, Personas, JTBD). Use at end of Phase 2 as convergence artifact. No new research - pure synthesis.
pm-process-flows
Identifies the system's user types (actors) and maps end-to-end processes - both a lean business process map per domain (for dev + design understanding) and per-user-type user flows connected to screens (a designer brief). User-type identification is adaptive - analyse the docs, confirm with the user, ask if unsure, or propose from context. Process maps reference entity states by name and do NOT duplicate them (low-maintenance). Phase 4-5 bridge into design; feeds pm-feature-design's UX context and the designer (impeccable / Figma).
pm-product-roadmap
Generate or update the Product Roadmap. Living document - v1 created in Phase 3b (vision + problem + business model), v2 updated in Phase 4 (domain constraints), v3 updated in Phase 5 (feature and delivery view). Run this skill at each update point.
pm-project-charter
Generate a Project Charter and Assumptions & Risks Register for a new product initiative. Use when starting Phase 1 of a Greenfield project.
pm-prototype
Cross-phase prototyping engine. Turns a scoped chunk of the product (a feature, a PRD initiative, the whole product, or any slice) into a tool-ready prototype spec that a prototyping tool (Lovable, v0/Vercel, Base44, Figma Make) can build with minimal loss of context. Gate-checks whether a prototype is worth it, ingests your ACs / flows / process / screens / feature card / brain dump, then compiles a tool-optimized build prompt. Pushes to the selected tool via MCP or hands you a paste-ready block. On re-run, captures the prototype result and feeds it back to the Feature Card / hypothesis register. Use anytime you want to validate before real build.
pm-reconcile-status
Progress dashboard for an in-flight reconciliation rebuild. Reads the Reconciliation Plan and state.json, shows which areas are done, in progress, and pending, surfaces open business-logic divergences that still need the team's decision, and routes to the next area command. Run it every time you sit down to a multi-session reconcile. Read-only - it changes nothing.
pm-reconcile
Rebuild playbook for an existing product onboarded to Pureinn. Reconciles the actual codebase against a folder of legacy documents (BRD, FSD, domain/entity models, business rules) that may contain logical, semantic and structural inconsistencies. Runs in two phases - first PLAN (inspect docs + code, define which areas to reconcile, in what order, into which Pureinn artifacts), then per-area EXECUTION (/pm-reconcile domain | rules | features ...) one layer at a time. Produces a living Reconciliation Report and rebuilds the 4 Live Registers + feature inventory clean. A closing verify pass (/pm-reconcile verify) re-reads the source one last time, proves every unit was transposed, incorporates any gaps it finds (not just reports them), and rules whether the legacy source is safe to archive - the source-disposal gate. The source is whatever the user points to (any format), never a hardcoded BRD. Use when a product was built outside the framework, has stale or conflicting docs, and the (often new) team needs one co
pm-reverse-extract
Migration path skill for products built outside the framework. Reads existing codebase, docs, and Feature Cards (if any) to extract the full feature inventory, including cross-feature Dependencies (user-stated + code-evidence-derived) and Priority - same fields, same Notion property set as pm-features-list, for structural parity across playbooks. Outputs feature_list.md (Live Register 4, FEAT-[DOMAIN]-NNN IDs) + stub Feature Cards in features/cards/ + Notion push. Run after pm-entity-registry and pm-business-rules-library have initialized the domain registers. Run instead of pm-features-list + pm-mvp-scope for existing products.
pm-scope-brief
Generate the Scope Brief - the definition document for a commissioned build. States what exactly will be built, for whom, within which constraints, and how done is judged. Phase 3b alternative to pm-prd when the mandate is already given (client engagement, exec directive) and full market validation + business model work is not needed. Carries a Business Capabilities section so Phase 4-5 skills (pm-entity-registry, pm-features-list) can consume it exactly as they consume a PRD.
pm-stakeholder-map
Generate a Stakeholder Map, RACI Matrix, and Escalation Tree for a product initiative. Use in Phase 1 after Project Charter is complete.
pm-stripe
JIT Delivery Stripe session orchestrator. Run every time you sit down to work on Phase 6-7. Reads current state across all active stripes, detects where each feature is in the lifecycle, surfaces the right next action, and routes you to the correct skill. One stripe = one isolated development channel. Features process one at a time per stripe in dependency order.
pm-team-roster
Generate a Team Roster, Decision Rights Matrix, and Skill Gap Assessment for a product initiative. Use in Phase 1 after Stakeholder Map.
pm-tech-feasibility
Generate a Tech Feasibility Report from raw research inputs. Use in Phase 2 (Track A) after collecting Perplexity/ChatGPT deep research and Tech Lead analysis.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.