backlog-expert

Agile issue generation from design specifications involves extracting atomic, verifiable tasks from user stories and business rules. This Skill automates parsing project documentation to create a structured backlog complete with issue IDs, priorities, and effort estimations.

Yes, you can create epics and group related issues from discovery briefs. The Skill organizes related atomic issues into broader epics for better project management, ensuring cross-references to design artifacts and user stories are maintained.

Automating task creation from user stories is best handled by converting text into actionable issues with defined priorities and effort estimations. This ensures the resulting backlog aligns directly with project requirements and design handoffs.

Yes, the generated backlog supports cross-references to design artifacts. The Skill explicitly manages issue IDs and cross-references to design artifacts and user stories, ensuring compatibility with board update scripts.

To estimate effort and set priorities for generated project issues, the Skill automatically assigns these values during issue creation. It processes project documentation to output a fully structured backlog ready for development.

Limitations when generating issues from project documentation include relying on the quality of input discovery briefs and design specs. If the source text lacks clear business rules or user stories, the generated atomic issues may require manual refinement.