pm-state

Generate auditable Mermaid state machine diagrams from PMContext lifecycle rules.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wcof/PMSkill --skill pm-state
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-state
Source: https://github.com/Wcof/PMSkill/tree/main/skills/visualization/pm-state
Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-state

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams turn scattered lifecycle rules in PMContext into a clear, traceable state machine diagram. It reduces ambiguity around entity states, transition conditions, failure paths, and terminal states so engineers can implement behavior without guessing.

Core Features & Use Cases

  • PMContext-to-state-machine generation: Extracts states, transitions, and trigger conditions from rules, data models, and business flows.
  • Exception-path coverage: Forces visibility of failure, timeout, cancellation, rollback, and illegal transition gaps that PM documents often miss.
  • Traceable delivery artifact: Produces Mermaid stateDiagram-v2 output plus state and transition tables with explicit source references or assumption markers.
  • Use Case: When defining an order, subscription, or content-review lifecycle, use this Skill to generate an implementation-ready state machine that exposes missing end states, rollback logic, and prohibited jumps before development starts.

Quick Start

Ask the AI to use pm-state on your PMContext to generate a Mermaid state machine with grouped entities, transition conditions, exception paths, and terminal states.

Frequently Asked Questions about pm-state

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a state machine diagram from product specifications?

To generate a state machine from product specifications, input your PMContext to extract entity states, transition rules, and lifecycle conditions. The skill outputs a Mermaid stateDiagram-v2 alongside traceable state and transition tables for implementation.

How do you model exception paths and rollback logic in a lifecycle state machine?

Modeling exception paths in a lifecycle state machine requires explicit annotation of failure, cancellation, timeout, and rollback states. The skill validates these illegal transitions against your business rules and highlights missing terminal states.

What is the best way to document order flow transitions and illegal states?

The best way to document order flow transitions is generating a Mermaid stateDiagram-v2 with source-traceable transition tables. This explicitly marks assumptions and annotates prohibited jumps to ensure engineers avoid implementing illegal state changes.

Can I use Mermaid stateDiagram-v2 to visualize subscription lifecycle conditions?

Yes, you can visualize subscription lifecycle conditions using Mermaid stateDiagram-v2. The skill extracts trigger conditions and terminal states from your PMContext, mapping the entire subscription flow including cancellation and timeout paths into the diagram.

Does this state machine generation approach work without external dependencies?

Yes, state machine generation works without external dependencies. It processes your PMContext internally to produce auditable diagrams and transition tables, requiring only Mermaid rendering support to visualize the output stateDiagram-v2 format.