prd-to-stories

To decompose a PRD into structured stories, this tool transforms product requirement documents into a Request, Epic, and Story hierarchy. It applies MECE granularity rules to ensure stories are implementation-ready for sprint planning and backlog preparation.

Converting feature-scoped PRDs into Feishu work items involves parsing the document to create Request, Epic, and Story tasks. It optionally uses Feishu MCP integration to check duplicates via MOQL, create work items, and record returned work_item_ids.

Yes, you can generate a stories.md backlog file from product requirements automatically. The tool outputs a structured markdown file containing the decomposed Request, Epic, and Story items for release and sprint-sync workflows.

Yes, this PRD decomposition tool checks for duplicate stories before creating Feishu tasks. It performs MOQL duplicate checks during the decomposition process and detects existing stories to prevent redundant backlog items.

If the Feishu MCP connection is unavailable, the PRD decomposition process handles the unavailability with a graceful downgrade. It still outputs the stories.md file locally, skipping the automatic creation of Feishu work items.

Yes, you need a specific directory structure to parse PRDs into implementation backlogs. The tool expects feature-scoped PRDs located under the portfolio/{product}/features/{feature}/prd path to correctly generate the backlog hierarchy.