create-requirement-ticket

Create GitHub issues with problem-first statements and numbered testable requirements.

Updated Mar 7, 2026

Search Tags:#github #specification #requirements #ticket #issue #product-management #acceptance-criteria

Ready to run

npx skills add https://github.com/korchasa/flowai-workflow --skill create-requirement-ticket

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-requirement-ticket
Source: https://github.com/korchasa/flowai-workflow/tree/main/.claude/skills/create-requirement-ticket
Command: npx skills add https://github.com/korchasa/flowai-workflow --skill create-requirement-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many GitHub issues conflate implementation details with requirements, causing scope creep, unclear acceptance criteria, and wasted engineering time; this Skill produces problem-first, implementation-agnostic requirement tickets that specify what must change and why.

Core Features & Use Cases

Problem-first tickets: Start with a concise problem statement describing current behavior, symptoms, and impact.
Behavioral requirements: Produce numbered, testable requirements that describe observable outcomes, not code or file locations.
Verifiable DoD: Include clear, quickly verifiable acceptance criteria that validate the solution without prescribing implementation.
Use case: Product managers or triage engineers drafting feature requests, bug reports, or change requests that must be handed to implementers without locking design choices.

Quick Start

Create a GitHub issue that states the problem, lists numbered testable requirements, and includes observable acceptance criteria without prescribing implementation.

Frequently Asked Questions about create-requirement-ticket

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

FAQPage Schema

How do I write GitHub requirement tickets without prescribing implementation details?▼

Write GitHub requirement tickets by starting with a concise problem statement that describes current behavior and impact, then listing numbered, testable behavioral requirements and observable acceptance criteria that validate the solution without referencing specific files or code locations.

Why do my GitHub issues cause scope creep and unclear acceptance criteria?▼

GitHub issues cause scope creep when they conflate implementation details with requirements. To fix this, create problem-first tickets that specify what must change and why, ensuring behavioral requirements describe observable outcomes rather than locking design choices.

What is a problem-first GitHub issue format for product managers and triage engineers?▼

A problem-first GitHub issue format captures problems and behavioral requirements without implementation language. It includes a concise problem statement, numbered testable requirements describing observable outcomes, and a verifiable definition of done that excludes file or line references.

How to create GitHub feature requests with testable acceptance criteria?▼

Create GitHub feature requests with testable acceptance criteria by drafting numbered behavioral requirements that describe observable outcomes. Include a verifiable definition of done that validates the solution quickly without prescribing implementation details or code locations.

Can I use this approach for bug reports and change requests on GitHub?▼

Yes, this approach works for bug reports and change requests on GitHub. It ensures problem-first statements and minimal scope, producing implementation-agnostic requirements suitable for product managers and stakeholders handing tickets to implementers.

When should I not include implementation language in GitHub issues?▼

You should not include implementation language in GitHub issues when writing requirement tickets for implementers. Exclude file, line, or implementation references to avoid locking design choices, and instead focus on observable behavioral requirements and verifiable acceptance criteria.