requirements-gathering

Name: requirements-gathering
Availability: InStock
Author: mcj-coder

Gather requirements through interactive questioning and create structured tickets.

1|1|Updated Jan 3, 2026

Search Tags:#requirements #agile #decomposition #issue tracking #scope definition #ticket creation

Ready to run

npx skills add https://github.com/mcj-coder/development-skills --skill requirements-gathering-mcj-coder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-gathering
Source: https://github.com/mcj-coder/development-skills/tree/main/skills/requirements-gathering
Command: npx skills add https://github.com/mcj-coder/development-skills --skill requirements-gathering-mcj-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the initial phase of software development by ensuring that requirements are clearly defined and captured in a work item before any design or implementation begins, preventing scope creep and ensuring clarity.

Core Features & Use Cases

Interactive Requirement Elicitation: Asks targeted questions to understand the "WHAT" and "WHY" of a feature or fix.
Structured Ticket Creation: Organizes gathered information into Goal, Requirements, Acceptance Criteria, and Context sections within a ticket.
Scope Decomposition: Identifies when a request is too large and proposes breaking it down into smaller, manageable tickets.
Platform Agnostic: Works with GitHub, Azure DevOps, and Jira.
Use Case: When a stakeholder requests a new feature, this Skill guides the conversation, asks clarifying questions, and creates a well-defined ticket in your issue tracker, ready for the next stage of development.

Quick Start

Use the requirements-gathering skill to define the scope for a new user authentication feature.

Frequently Asked Questions about requirements-gathering

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

FAQPage Schema

How do I capture requirements and structure them into a ticket format for agile development?▼

To capture requirements, this Skill uses interactive questioning to define the "WHAT" and "WHY" of new work items, then structures the responses into a ticket format containing Goal, Requirements, Acceptance Criteria, and Context sections.

What is the best way to decompose large tasks into epics and child tickets?▼

Decomposing large tasks into epics and child tickets is handled through scope definition, where the Skill identifies oversized requests and proposes breaking them down into smaller, manageable tickets to prevent scope creep before design begins.

Does requirements gathering work with Jira, Azure DevOps, and GitHub issue tracking?▼

Yes, requirements gathering works with Jira, Azure DevOps, and GitHub issue tracking through platform-agnostic CLI integration, allowing you to create well-defined tickets directly in your chosen issue tracker.

Can I use this Skill to plan implementation and design after creating tickets?▼

No, you cannot use this Skill to plan implementation or design after creating tickets, because it enforces an issue-driven development workflow that stops immediately after ticket creation without proceeding further.