ba-user-story-spec

Automate user story documentation by aggregating data from UI specs, sequence diagrams, and activity diagrams into a standardized 7-section Markdown file. The workflow auto-checks and fetches missing information from related skills, saving the complete document to a designated folder for immediate sharing.

Generate use case documents by providing an Epic and a function to automatically assemble a 7-section Markdown file. This process integrates UI details, API specs, and workflow diagrams, ensuring comprehensive documentation is compiled and stored in the specified User Story folder.

Yes, you can export the generated Markdown use case documentation to DOCX format or publish it directly to Confluence. The Skill uses python-docx and markdown dependencies to convert and export the assembled 7-section document after saving it to the designated folder.

Yes, the user story generation tool automatically checks for missing information and fetches it by coordinating with related skills. This reduces manual follow-ups when data from UI specs, sequence diagrams, or activity diagrams is incomplete during the aggregation process.

Structure use case documentation using a standardized 7-section Markdown format that aggregates UI specifications, sequence diagrams, and activity diagrams. This enforces a consistent structure across the team, synthesizing scattered data into a single comprehensive User Story document.

The aggregation requires existing UI specs, sequence diagrams, and activity diagrams to fetch missing data from related skills. If related skills cannot provide the missing information, the 7-section Markdown output may remain incomplete, requiring manual data entry before DOCX export.