wtf.write-epic

Drafts Word.epic documents with goals, metrics, and GitHub issue integration via CLI.

7|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/xiduzo/wtf --skill wtf-write-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wtf.write-epic
Source: https://github.com/xiduzo/wtf/tree/main/skills/wtf.write-epic
Command: npx skills add https://github.com/xiduzo/wtf --skill wtf-write-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams translate strategic ideas into well-structured GitHub Epics, aligning stakeholders, goals, and a clear plan to drive multi-feature initiatives.

Core Features & Use Cases

  • Domain-driven Epic drafting: Produce a complete Epic body with goals, success metrics, bounded context, and a feature scaffold.
  • Structured inquiry workflow: Guide stakeholders through scoped questions to clarify boundaries, constraints, and dependencies.
  • GitHub integration & governance: Prepare issues that can be created via the GitHub CLI, with clear links to blockers and related epics.

Quick Start

Provide a seed idea for a strategic initiative and let the skill guide you through research, drafting, and issue creation.

Frequently Asked Questions about wtf.write-epic

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

FAQPage Schema
How do I write strategic Epics for GitHub initiatives that span multiple teams?

To draft GitHub Epics, provide a seed idea for a strategic initiative and the structured inquiry workflow will guide stakeholders through questions to clarify boundaries, constraints, and dependencies before generating the issue.

Can I use domain-driven design to structure product goals in GitHub issues?

Yes, domain-driven design structures product goals in GitHub issues by defining bounded contexts, outlining success metrics, and scaffolding features to ensure clear boundaries for multi-team initiatives.

Does this Epic drafting workflow integrate directly with the GitHub CLI?

Yes, the Epic drafting workflow integrates with the GitHub CLI to prepare issues for creation, automatically suggesting dependencies and linking blockers to related epics for governance.

What is the best way to align stakeholders when planning complex feature dependencies?

The best way to align stakeholders on complex dependencies is using a structured inquiry workflow that scopes questions to clarify boundaries, outline goals, and map blockers before creating GitHub issues.

When should I use an Epic instead of a standard GitHub issue for product planning?

Use an Epic instead of a standard GitHub issue when defining strategic initiatives that span teams, require stakeholder alignment, and need to outline goals, success metrics, and bounded contexts.