pureinn.docs

Pureinn Documentation

/plugin marketplace add ljucask/pureinn-product-development

Pureinn is an AI-native product development framework for Claude Code. It covers the full product lifecycle - from the first idea to a shipped product - through 50 skills and a structured three-playbook engine.


Install

/plugin marketplace add ljucask/pureinn-product-development
/plugin install pureinn-product-development@pureinn-product-development

Select user scope to make it available across all projects.


Quick start

/pureinn "your product idea"

The engine scans your workspace, asks 9 intake questions, selects the right playbook, and presents an ordered skill queue. Run skills one at a time. Run /pureinn again after each phase to check the exit gate and advance.

/pureinn-resume [project-slug]    # resume a paused project (omit slug to list all)
/pureinn map                      # full framework overview - all playbooks, phases, skills

Three playbooks

PlaybookUse when
GreenfieldNew product, zero users, validating PMF
Feature ImplementationProduct exists, active users, adding new functionality
RebuildOnboarding an existing product into Pureinn (legacy docs or clean)

Run /pureinn [product idea] and the engine routes you automatically.


Fast tracks

Skip phases you don't need.

Greenfield Express - validated idea, skip discovery:

/pureinn "your idea"          # workspace setup
/pm-entity-registry           # lean entity list
/pm-business-rules-library    # core rules, Draft mode
/pm-features-list             # feature inventory + FEAT-IDs
/pm-mvp-scope                 # MVP scope + Delivery Stripes
/pm-feature-design [ID]       # JIT spec per feature → build

Feature Implementation - first run on an existing codebase:

/pureinn [project]            # workspace setup
/common-ground                # tech context from existing code
/pm-reverse-extract           # bootstrap registers + feature inventory from codebase
/pm-feature-design [ID]       # JIT spec → build

Stage shortcuts

Jump straight into one part of the framework:

/pureinn define                        # current project → Commercial Definition
/pureinn acme model                    # named project → Domain Modeling
/pureinn discover "food delivery app"  # fresh project → Discovery
KeywordEntersYou exit with
setupPhase 1 - FoundationProject skeleton
discoverPhase 2 - DiscoveryMarket / personas / JTBD / domain understanding
validatePhase 3a - ValidationGo/No-Go verdict
definePhase 3b - Commercial DefinitionValue prop, business model, KPIs, PRD
modelPhase 4 - Domain ModelingEntities, rules, flows blueprint
planPhase 5 - Feature PlanningFeature list, KANO/V×C, MVP scope
buildPhase 6+7 - JIT DeliveryPer-feature spec + delivery

For a single artifact, run its skill directly - no stage keyword needed.


Agent mode

Any skill accepts --agent. Instead of running interactively, the skill drafts the artifact autonomously from existing inputs and returns a short summary for your review.

/pm-prd --agent
/pm-market-analysis --agent

Missing inputs are never invented - they're marked [ASSUMED]. No flag = interactive (default). See how it works.


Framework phases

PhaseWhat happensDuration
Phase 1 - FoundationProject charter, team, stakeholders~1 day
Phase 2 - DiscoveryMarket, tech, domain, customer research1-3 weeks
Phase 3a - ValidationHypothesis testing, Go/No-Go verdictExternally paced
Phase 3b - Commercial DefinitionBusiness model, KPIs, PRDHours to a few sessions
Phase 4 - Domain ModelingEntities, business rules, process flows3-5 days
Phase 5 - Feature PlanningFeature list, prioritization, MVP scope2-3 days
Phase 6+7 - JIT DeliveryPer-feature spec + build cycleOngoing
Cross-phase skillsPrototype, stress-test, root-cause, audit, meeting, onboarding, diagrams, glossary, stripeAny time
RebuildOnboarding an existing productVaries

Cross-phase skills at a glance

Skills that run at any point in any playbook - not tied to a phase:

SkillWhen to use
/pm-prototypeBefore any build commitment - compile a tool-ready prompt for Lovable / v0 / Figma Make
/pm-stress-testBefore exec reviews, investor pitches, board meetings, or any room where you'll be challenged
/pm-root-causeWhen a live metric drops, churn spikes, or a feature isn't being adopted
/pm-auditAfter research injection, re-prioritization, or before a build commitment or pitch
/pm-meetingAfter any meeting - generates structured summary + action items, pushes to Notion
/pm-onboardingWhen a new team member joins - generates a role-specific onboarding brief
/pm-diagramsWhen a visual is needed (user flow, architecture, ERD, JTBD forces)
/pm-glossaryStart early, update whenever new domain terminology surfaces
/pm-stripeOrchestrate and monitor the JIT delivery cycle across all active Delivery Stripes