define-requirements

To define feature requirements, you can use a structured Jobs-to-be-Done discovery process that interviews users to understand the problem, analyzes the codebase for impact, and prepares a TDD-focused implementation plan for GitHub issues.

The Jobs-to-be-Done approach for feature planning is a structured interview process that elicits problem statements and user jobs, ensuring new features are well-defined and aligned with actual user needs before any code is written.

You can create a GitHub issue-ready implementation plan by initiating a problem description, conducting JTBD interviews to map requirements, analyzing the codebase for implementation impact, and formatting the results into a TDD-focused plan.

Yes, codebase analysis is performed during the requirement definition process to map the exact implementation impact, ensuring the resulting feature plan aligns with existing project standards and conventions.

Yes, the requirement definition process explicitly supports test-driven development by delivering a TDD-focused implementation plan that translates JTBD discovery and codebase analysis into actionable testing and coding steps.

You need to use JTBD discovery when planning new features or documenting requirements, specifically to validate that you understand the core problem and user jobs before committing to an implementation plan.