Generate structured Agile Epic Markdown documents from initiative details.
npx skills add https://github.com/epieczko/betty --skill epic-write
Please help me install this Agent Skill. Skill: epic.write Source: https://github.com/epieczko/betty/tree/main/skills/epic.write Command: npx skills add https://github.com/epieczko/betty --skill epic-write
Generate an Agile Epic from a high-level goal, feature request, or strategic initiative, producing a structured Markdown epic document that aligns with Agile best practices.
python3 skills/epic/write/epic_write.py
--initiative_name_(string,_required):the_overarching_initiative_or_product_goal "Customer Self-Service Portal"
--context(string,_required):_relevant_background,_rationale,and_success_criteria "Enable customers to manage accounts"
--stakeholders(array_of_strings,_required):_who_cares_about_this_and_why "Product Team,Engineering" \
High-intent search queries and answers about installing and using this skill.
epic.write transforms high-level goals into structured Agile Epic documents by accepting an initiative name, context, and stakeholders as input, then outputs a formatted Markdown file with sections for title, summary, background, acceptance criteria, stakeholders, and next steps aligned to Agile best practices.
Provide the initiative name or product goal, relevant background and success criteria, and stakeholder list. epic.write validates these required fields and generates a complete Epic document with metadata tags for artifact tracking and downstream decomposition guidance.
Yes. epic.write automates Agile Epic creation by processing initiative details through a structured workflow that produces Markdown-formatted epics with acceptance criteria, stakeholder mapping, and timestamps, eliminating manual documentation for product management workflows.
epic.write generates Markdown-formatted Epic documents saved as epic.md by default, containing standardized sections including title, summary, background, acceptance criteria, stakeholders, and next steps, with embedded metadata for artifact tracking in Agile workflows.
No. While epic.write depends on JSON and YAML processing internally, you only provide inputs as command-line arguments—initiative name, context, and stakeholders—and receive a ready-to-use Markdown Epic document without direct interaction with those formats.
epic.write includes creation timestamps and metadata tagged as agile-epic, enabling downstream decomposition into user stories and sprint planning while maintaining traceability links between the strategic initiative and implementation artifacts.
pradyumnasagarAutomate inter-skill data transfer and provenance capture via JSON Material Passports.
JingyiWngGenerate sprint-status.yaml from epic markdown files with validated YAML output.
epieczkoParse Markdown Epic documents and generate structured user stories as JSON.
tapanshahGenerates INVEST-compliant user stories with acceptance criteria and sprint plans.
