requirements-analysis

The requirements-analysis skill helps identify and diagnose requirements-level problems in software projects before implementation begins. It focuses on uncovering the real problems that need solving rather than jumping directly to solutions or feature lists. By treating requirements as hypotheses rather than fixed truths, the skill guides users toward understanding who is affected by a problem, why the problem exists, and whether proposed requirements actually address underlying needs. This approach helps reduce the risk of building solutions that fail to solve meaningful problems.

The skill provides structured diagnostic guidance through several requirement analysis states. It helps users move from having no clear problem statement, to avoiding solution-first thinking, to refining vague needs into testable requirements, and to identifying hidden constraints and assumptions. It uses targeted questions and interventions such as Jobs-to-be-Done self-interviews, problem archaeology, function extraction, acceptance scenario writing, testability checks, constraint inventories, and assumption mapping. These techniques are designed to improve clarity, reveal overlooked dependencies, and distinguish real constraints from preferences.

This skill is useful for solo developers, software project founders, and anyone defining requirements for a new product, feature, or initiative. Common use cases include validating product ideas, clarifying user problems, evaluating proposed features, identifying project risks, and discovering hidden assumptions before development starts. It is particularly valuable in early-stage planning and discovery activities where requirements are uncertain or poorly defined.