skills.rest
xiduzo
xiduzoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

wtf.write-feature

Convert Epics into domain-aligned GitHub Features with acceptance criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Breaks down Epics into concrete, domain-language GitHub Features by pulling context from the parent Epic and guiding naming, acceptance criteria, and scope so teams can plan and implement with a shared contract.

Core Features & Use Cases

  • Create a single Feature issue that defines a user-facing capability and fetches its parent Epic for context.
  • Name the capability in domain terms (Domain Actor can [verb] [object]) to ensure ubiquitous language.
  • Generate 2–4 user stories in the "As a Domain Actor, I want ..." format aligned to the Epic's goals.
  • Enforce DoR, perform a vertical-slice scope check, and draft an end-to-end Feature body ready for tasking.

Quick Start

Provide the Epic reference and the domain-language capability you want to create as a Feature.

Frequently Asked Questions about wtf.write-feature

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

FAQPage Schema
How do I break down an Epic into domain-aligned GitHub Features?▼

To break down an Epic into domain-aligned GitHub Features, provide the Epic reference and the intended capability. The tool pulls parent Epic context to generate a Feature issue with domain-language naming, acceptance criteria, and a clear scope.

What is domain-driven design naming for GitHub issue Features?▼

Domain-driven design naming for GitHub Features uses the format 'Domain Actor can [verb] [object]' to ensure ubiquitous language. This captures the domain actor, bounded context, and key events within the generated Feature body.

How do I write acceptance criteria for a GitHub Feature issue?▼

Writing acceptance criteria for a GitHub Feature issue involves generating 2–4 user stories in the 'As a Domain Actor, I want ...' format. This enforces the Definition of Ready and aligns the stories directly to the parent Epic's goals.

Can I link a GitHub Feature issue to its parent Epic automatically?▼

Yes, you can link a GitHub Feature issue to its parent Epic. Provide the Epic reference during creation, and the resulting Feature is prepared with links to the Epic context and related artifacts for shared team planning.

Does this Epic breakdown approach enforce Definition of Ready and scope checks?▼

Yes, this Epic breakdown approach enforces the Definition of Ready and performs a vertical-slice scope check. It drafts an end-to-end Feature body that is ready for tasking and implementation with a shared contract.

Related Skills

Explore More Product & Management Skills→
lluppesmslluppesms

breakdown-feature-prd

Generate structured Markdown PRDs from Epic feature descriptions.

Community
Intermediate
guardiatechnologyguardiatechnology

kata-plan-task

Create a linked GitHub Plan sub-issue from a validated parent issue.

Official
Intermediate
DhumitechDhumitech

ddd-strategic-design

Classify domain capabilities and subdomains into bounded contexts with ADR rationales.

Community
Intermediate
rnaarlarnaarla

to-prd

Generate a PRD from conversation context and publish it to the issue tracker.

Community
Advanced