writing-tickets

Translate project specs into structured epics and tasks with acceptance criteria.

Updated Jan 12, 2021
One-click install
npx skills add https://github.com/jssee/.dotfiles --skill writing-tickets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-tickets
Source: https://github.com/jssee/.dotfiles/tree/main/.config/opencode/skill/writing-tickets
Command: npx skills add https://github.com/jssee/.dotfiles --skill writing-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams turn ambiguous specs or requirements into clear, actionable tickets so engineers can begin work with confidence and minimal context.

Core Features & Use Cases

  • Structured Epics & Tasks: Break work into epic-level goals and discrete tasks with explicit dependencies.
  • Acceptance Criteria & Guidance: Each ticket includes acceptance criteria, files to touch, testing steps, and reference docs.
  • Workflow for Execution: Supports an execution handoff with a suggested ticket lifecycle and optional subagent-assisted workflow.

Quick Start

Use the writing-tickets skill to generate a set of tickets from a given spec.

Frequently Asked Questions about writing-tickets

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

FAQPage Schema
How do I turn project specs into actionable engineering tickets?

To turn project specs into actionable engineering tickets, you translate multi-step requirements into a structured plan with discrete tasks, explicit dependencies, and clear acceptance criteria. This ensures engineers start work with minimal context.

What is the best way to break down an epic into tasks with acceptance criteria?

Breaking down an epic into tasks with acceptance criteria involves structuring epic-level goals into discrete tasks that include precise file touchpoints, code snippets, testing steps, and documentation notes for clear execution handoff.

How do you write testing steps and file touchpoints for a development task?

Writing testing steps and file touchpoints for a development task requires specifying exact files to modify, providing reference code snippets, and outlining validation procedures within each ticket's acceptance criteria.

Can I generate a full ticketing plan from a multi-step product requirement?

Yes, you can generate a full ticketing plan from a multi-step product requirement. The process creates structured epics and tasks with defined owners, dependencies, and a suggested lifecycle for execution handoff.

Does this ticket generation approach support subagent-assisted workflows?

Yes, this ticket generation approach supports an execution handoff with a defined ticket lifecycle and an optional subagent-assisted workflow to guide engineering teams through task completion.