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.…
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.
Structure validation hypotheses, design low-cost experiments, track results, and produce a Go/No-Go decision. Runs in Phase 3a: Plan mode structures hypotheses and experiments, Results mode records outcomes and issues the Go/No-Go verdict (hard gate before Phase 3b). Based on a 5-stage SaaS validation framework.
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.
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.
Generate Market Size Analysis (TAM/SAM/SOM), Competitor Analysis, SWOT, and Market Timing Rationale from raw research inputs. Use in Phase 2 (Track C).
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…
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 featurelist.md and Feature Card frontmatter (phase + stripe). If features already…
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…
Build and maintain the Open Questions & Decisions Register - Live Register 5 in the FDD+SDD framework. Centralizes every unresolved question, legacy-vs-code divergence, and concrete blocker across the whole project into one file (/domain/openquestions.md), each with a unique ID (OQ-/DIV-/BLK-{DOMAIN}-NN), full…
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…
Two modes. (1) Product PRD - Phase 3b exit artifact synthesizing all Phase 2+3a+3b outputs. Saves to product/PRDmaster.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.…
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…
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.
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.
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…
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.
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…
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…
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…
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…