pm-task-writer

Name: pm-task-writer
Availability: InStock
Author: Warpcode

Translate epics into user stories and Gherkin acceptance criteria.

2|2|Updated Apr 7, 2013

Search Tags:#acceptance criteria #user stories #bdd #gherkin

Ready to run

npx skills add https://github.com/warpcode/dotfiles --skill pm-task-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-task-writer
Source: https://github.com/warpcode/dotfiles/tree/main/generic/.config/opencode/skills/pm-task-writer
Command: npx skills add https://github.com/warpcode/dotfiles --skill pm-task-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates user stories from epics and writes testable acceptance criteria in Gherkin format.

Core Features & Use Cases

Translate features into structured user stories using the standard format.
Produce acceptance criteria in Given/When/Then style for testability.
Propose follow-ups for deeper technical analysis.

Quick Start

Create a set of user stories from an epic and outline acceptance criteria in Gherkin.

Frequently Asked Questions about pm-task-writer

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

FAQPage Schema

How do I write user stories from an epic?▼

User stories translate epics into actionable work by breaking down features into the 'As a [user type], I want [action] so that [benefit]' format. This structure clarifies who needs what and why, making requirements testable and scope-bounded for sprint planning and backlog grooming.

What are acceptance criteria in Gherkin format and why use them?▼

Gherkin acceptance criteria use Given/When/Then syntax to define testable conditions for user stories. This format makes test cases executable and ensures QA, developers, and product teams share a common understanding of done before work begins.

When should I break down epics into user stories?▼

Break epics into user stories during feature breakdown, backlog grooming, and sprint planning to create manageable, deliverable units. This prevents scope creep, enables parallel work, and provides clear acceptance criteria for QA and verification.

Can I use Gherkin acceptance criteria with BDD workflows?▼

Yes. Gherkin acceptance criteria align directly with Behavior-Driven Development practices, allowing acceptance criteria to double as executable test scenarios and documentation for feature validation.

What comes after defining acceptance criteria?▼

After acceptance criteria are defined, conduct deeper technical analysis, design review, and verification planning. The Skill recommends next steps for implementation scoping and QA validation before development begins.