requirements

Guide JTBD interviews and generate GitHub issue handoffs for feature requirements.

4|1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/MattVOLTA/outworkos_diy --skill requirements-mattvolta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements
Source: https://github.com/MattVOLTA/outworkos_diy/tree/main/skills/requirements
Command: npx skills add https://github.com/MattVOLTA/outworkos_diy --skill requirements-mattvolta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams define well-structured feature requirements before implementation by guiding problem definitions and Jobs-to-be-Done (JTBD) interviews, ensuring clarity and alignment early in the development process.

Core Features & Use Cases

  • Problem Definition interviews to understand the core problem and scope.
  • JTBD mapping to identify user goals and the jobs users need to accomplish.
  • Codebase impact analysis to assess changes required and risk.
  • Implementation planning with test-driven development (TDD) oriented recommendations.
  • GitHub issue handoff generation to prepare ready-to-create issues with acceptance criteria.
  • workflow guidance and project-conventions alignment via CLAUDE.md references.

Quick Start

Start structured feature discovery by defining the problem and JTBD through guided prompts, then generate a handoff-ready GitHub issue.

Frequently Asked Questions about requirements

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

FAQPage Schema
How do I define feature requirements using JTBD interviews?

Feature requirements using JTBD interviews are defined by guiding problem-definition sessions to clarify problems, map user jobs, analyze codebase impact, and prepare implementation plans. This structured approach ensures alignment early in product planning.

What is the best way to map user jobs for product planning?

Mapping user jobs for product planning involves running structured JTBD interviews to identify user goals and the specific jobs users need to accomplish. This process clarifies the core problem and scope before implementation begins.

How do I generate a GitHub handoff issue with acceptance criteria?

Generating a GitHub handoff issue requires completing problem definition and JTBD mapping, which then produces a ready-to-create GitHub issue artifact containing acceptance criteria and implementation plan details.

Does this requirements discovery process align with project conventions?

The requirements discovery process aligns with project conventions by referencing CLAUDE.md, ensuring workflow guidance and project-specific rules are followed during implementation planning and codebase impact analysis.

Can I get codebase impact analysis before implementation planning?

Codebase impact analysis is performed during early product planning to assess required changes and risks. It directly informs the subsequent implementation planning phase with test-driven development oriented recommendations.

Why use structured problem definition for feature discovery?

Structured problem definition for feature discovery clarifies the core problem and scope before development. It guides JTBD mapping and codebase analysis to ensure well-structured feature requirements and alignment.