Provides an issue tracker exporter that automatically syncs generated product backlog items with GitHub Issues.
Provides an issue tracker exporter that automatically syncs generated product backlog items with Jira issues.
Provides an issue tracker exporter that automatically syncs generated product backlog items with Linear issues.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@PMFlow MCP generate a PRD for Apple Pay checkout with measurable KPIs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Autonomous Product Management Workflow, PRD Engine & BDD Story Validator for AI Agents
PMFlow MCP gives AI agents (Claude Desktop, Cursor, Devin, Roo-Code) the capabilities of a Senior Technical Product Manager. It generates structured Product Requirement Documents (PRDs), decomposes epics into testable User Stories, validates Given/When/Then acceptance criteria for testability, and exports markdown backlogs.
Automated PRD Generator (generate_prd): Creates complete PRD specifications with MoSCoW prioritization, functional requirements, technical constraints, risks, and measurable KPIs.
Atomic Story Decomposer (decompose_stories): Formats requirements into standard agile format: "As a [persona], I want [goal], so that [benefit]" with estimated story points.
BDD/Gherkin Syntax Validator (validate_acceptance_criteria): Enforces Given/When/Then syntax, flags ambiguous terms (e.g., "fast", "intuitive", "easy") that cause agent drift, and calculates a 0-100 testability score.
Markdown Specification Exporter (export_markdown_specs): Generates clean, commit-ready documentation for repositories.
Related MCP server: Agile Planner MCP Server
git clone https://github.com/johannschiffer/pmflow-mcp.git
cd pmflow-mcp
pip install -e .Add to your claude_desktop_config.json:
{
"mcpServers": {
"pmflow": {
"command": "python3",
"args": ["-m", "pmflow.server"]
}
}
}# Generate a PRD in Markdown
pmflow prd \
--title "Payment Gateway Integration" \
--problem "Customers cannot check out with Apple Pay" \
--audience "Mobile checkout shoppers" \
--features "Stripe SDK setup" "Apple Pay button" "Webhook listener" \
--markdown
# Validate BDD Acceptance Criteria
pmflow validate --criteria \
"Given user is on checkout page" \
"When user taps Apple Pay button" \
"Then payment sheet opens within 300ms"Need enterprise capabilities for multi-agent swarms? Check out PMFlow Pro:
User Story Dependency DAG Engine: Cycle detection via Kahn's algorithm and critical path calculation in SQLite WAL.
Sprint Velocity & Capacity Forecaster: Monte Carlo simulation of agent capacity and bottleneck alerts.
Issue Tracker Exporter: Automatic sync with Jira, Linear, and GitHub Issues.
Docker Compose: Production containerization ready for agent clusters.
Available at Gumroad.
MIT © Johann Schiffer
Decomposes a requirement into an atomic User Story with BDD Given/When/Then acceptance criteria.
Inputs: goal (required), title (required), benefit (required), persona (required), +4 more.
Exports structured PRD and story backlog into standardized Markdown documentation.
Inputs: prd, stories.
Generates a structured, production-ready PRD with requirements, tech stack, constraints, and success metrics.
Inputs: title (required), key_features (required), target_audience (required), problem_statement (required), +2 more.
Validates acceptance criteria syntax (Given/When/Then) and flags non-testable or ambiguous language.
Inputs: criteria (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool targets a distinct artifact and action in the pipeline: PRD generation, story decomposition, criteria validation, and markdown export. There is no meaningful overlap, so an agent can select the right tool unambiguously.
All four tools follow a consistent snake_case verb_noun pattern (generate_prd, decompose_stories, validate_acceptance_criteria, export_markdown_specs). The convention is uniform and predictable.
Four tools map cleanly onto the generate-decompose-validate-export pipeline, which is well-scoped rather than bloated. It is slightly thin, but each tool clearly earns its place.
The core generation pipeline is covered, but there are no read/update/delete operations, so an agent cannot retrieve, revise, or list existing PRDs and stories. This is a notable gap for a document-authoring workflow.
Turn PRDs and product ideas into structured specs so coding agents build your intent, not theirs.
Generate architecture docs, implementation plans, and dev tickets from your project requirements.
Tasks, sprints, releases and docs for engineering teams with AI coding agents.
Your team's stories, acceptance criteria, designs and docs, for coding agents. Sign in with OAuth.
