prod-backlog-generator

To convert requirements into executable user stories, you need a backlog generator that produces US-* and HUS-* stories with Given-When-Then acceptance criteria, YAML metadata, and dependency mapping for clear ownership and delivery planning.

Mapping dependencies and blockers when slicing vertical stories requires capturing blocked_by, blocks, and sibling links within each story's metadata, ensuring teams understand execution order and resolve blockers before implementation.

Generating human handoff stories for junior developers involves creating HUS-* stories from approved architecture, complete with junior-level task descriptions, evidence expectations, and mandatory human review for initial full plans.

Yes, using YAML story metadata and Given-When-Then formatting for product backlog automation enforces structured quality gates, evidence expectations, and consistent story placement in status folders for delivery tracking.

Templates needed for story splitting and follow-up workflows include user and human story templates, dependency mapping rules, and status folder placement guidance to maintain backlog structure and track evidence expectations.

You should not use automated user story generation when requirements are not yet approved or architecture is incomplete, as the process depends on stable inputs to produce accurate dependency mapping and executable acceptance criteria.