ba-user-story-spec

Consolidate UI specs, sequence diagrams, and activity diagrams into a seven-section markdown document.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill ba-user-story-spec-clovernguyen1010-ship-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ba-user-story-spec
Source: https://github.com/clovernguyen1010-ship-it/Clover_Nguyen/tree/main/.agent/skills/ba-user-story-spec
Command: npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill ba-user-story-spec-clovernguyen1010-ship-it

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, markdown, python-docx, and includes scripts (resource) components.

What problem does it solve?

This Skill serves as a centralized orchestrator to generate complete User Story/Use Case documentation by aggregating data from existing UI specs, sequence diagrams, and activity diagrams, and by prompting for missing information from related skills when needed.

Core Features & Use Cases

  • Aggregates information from UI specs, sequence diagrams, and activity diagrams to produce a complete 7-section User Story/Use Case document.
  • Detects gaps and coordinates related skills to fill missing details automatically within the defined workflow.
  • Supports optional AC formats and downstream exports (DOCX or Confluence) per user choice.

Quick Start

Provide a complete User Story/Use Case document by consolidating existing specs and auto-sourcing missing information from related skills.

Frequently Asked Questions about ba-user-story-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consolidate UI specs, sequence diagrams, and activity diagrams into one user story document?

To consolidate user story documentation, this Skill aggregates existing UI specs, sequence diagrams, and activity diagrams into a unified seven-section markdown file. It detects missing information and automatically coordinates related skills to fill the gaps.

Can I export user story markdown to DOCX or Confluence?

Yes, you can export user story markdown to DOCX or Confluence. The Skill supports optional acceptance criteria formats and provides downstream exports to DOCX using python-docx or Confluence, depending on your chosen workflow configuration.

How do I generate use case documentation that includes acceptance criteria?

To generate use case documentation with acceptance criteria, the Skill assembles a complete document from existing diagrams and UI specs while supporting optional AC-based formats. It standardizes the output into a structured markdown file for immediate use.

What is the best way to identify missing information in use case documentation?

Identifying missing information in use case documentation is handled by the Skill's gap detection mechanism. It analyzes aggregated UI specs and diagrams, then invokes related skills to automatically supply the missing details within the defined workflow.

Does generating user story documentation require sequence and activity diagrams?

Generating user story documentation does not strictly require sequence and activity diagrams upfront. The Skill consolidates available UI specs and diagrams, and if gaps are detected, it coordinates with related skills to source the missing information automatically.

Why use an orchestrator for use case documentation instead of manual markdown?

An orchestrator for use case documentation centralizes aggregation from multiple sources like UI specs and diagrams, unlike manual markdown. It standardizes the seven-section output, detects gaps, and auto-sources missing data from related skills to ensure completeness.