PMFlow MCP

decompose_stories

Splits a requirement into an atomic user story with BDD Given/When/Then acceptance criteria, producing testable backlog items for agile planning.

Instructions

Decomposes a requirement into an atomic User Story with BDD Given/When/Then acceptance criteria.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "story_id": "<story_id>",
      "title": "<title>",
      "persona": "<persona>",
      "goal": "<goal>",
      "benefit": "<benefit>",
      "acceptance_criteria": "<acceptance_criteria>"
    },
    "name": "decompose_stories"
  }
}

Input Schema

Name	Required	Description
`goal`	Yes	Action the user wants to take
`title`	Yes	Short title of the user story
`benefit`	Yes	Underlying business or technical value
`persona`	Yes	User role (e.g., DevOps Engineer)
`story_id`	Yes	Unique identifier (e.g. US-001)
`depends_on`	No	List of parent story IDs
`story_points`	No	Estimated complexity points (default 3)
`acceptance_criteria`	Yes	List of Gherkin steps (Given/When/Then)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 21, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden of behavioral disclosure, yet it only says what is produced. It does not say whether anything is persisted, whether the call is idempotent, whether output is returned inline or written to a file, or whether it mutates existing stories. For a 6-required-parameter generation tool with zero annotation coverage, that is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the key output characteristic (atomic story with BDD criteria) is stated up front. It is efficient, though its brevity is partly a symptom of under-specification rather than deliberate economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a transformation/generation tool with 8 parameters, no annotations, and no output schema, the description omits prerequisites, side effects, and what the caller receives back. An agent cannot tell from this text whether the tool writes a ticket, returns JSON, or requires a prior PRD step.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all 8 parameters are already documented in the schema, establishing a baseline of 3. The description only adds the notions 'atomic' and 'BDD Given/When/Then acceptance criteria', which loosely maps to the acceptance_criteria field but gives no new syntax or constraint detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (decomposes) and resource (a requirement into an atomic User Story) and even names the output artifact's format (BDD Given/When/Then criteria). It does not, however, differentiate itself from siblings like generate_prd or validate_acceptance_criteria, which an agent could easily confuse with this one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or prerequisite guidance. The description never says whether a PRD or requirement document must exist first, nor why an agent would pick this over validate_acceptance_criteria or generate_prd.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server