wtf.write-task

Convert a Feature into a GitHub Task with Gherkin scenarios.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert a Feature into an actionable GitHub Task by deriving Gherkin scenarios from the Feature's Acceptance Criteria, enforcing domain language, and validating vertical-slice integrity and task dependencies to ensure a coherent, single-end-to-end work item.

Core Features & Use Cases

  • Derives Gherkin scenarios directly from the parent Feature's Acceptance Criteria and integrates them into Task definitions.
  • Guides creation of a GitHub Task issue linked to a parent Feature and Epic, maintaining the project’s domain language.
  • Enforces DDD ubiquitous language in scenarios and checks vertical-slice integrity to prevent scope creep.
  • Evaluates task dependencies and signals cross-feature implications to maintain proper sequencing within an Epic.
  • Provides a structured, step-by-step process from identifying the parent Feature to drafting the Task and preparing it for creation.

Quick Start

Draft a concrete Task description derived from the Feature's ACs and review it before creating a GitHub Task issue.

Frequently Asked Questions about wtf.write-task

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

FAQPage Schema
How do I convert feature acceptance criteria into GitHub tasks?

To convert features into GitHub tasks, derive Gherkin scenarios directly from the feature's acceptance criteria. This enforces domain language and validates vertical-slice integrity to draft a structured, independently shippable task issue.

How do I write Gherkin scenarios from acceptance criteria for task creation?

Writing Gherkin scenarios from acceptance criteria involves enforcing ubiquitous domain language and applying cross-checks. Dependency and vertical slice checks ensure the resulting task represents a single, end-to-end work item ready for GitHub.

What is a vertical slice check in task creation and when do I need it?

A vertical slice check in task creation ensures an issue represents a single, end-to-end, independently shippable work item. You need it when deriving tasks from features to prevent scope creep and maintain proper sequencing within an Epic.

Can I enforce DDD ubiquitous language when generating GitHub issues?

Yes, you can enforce DDD ubiquitous language when generating GitHub issues. The task creation process integrates domain language directly into the Gherkin scenarios derived from the parent feature's acceptance criteria.

How do I evaluate task dependencies within an Epic before creating issues?

To evaluate task dependencies within an Epic, cross-check the task scope against parent features and consult contracts. This signals cross-feature implications to maintain proper sequencing and ensures coherent work item creation.