requirements-development-process

Orchestrates the end-to-end requirements development lifecycle from vision through validated baseline.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-development-process-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-development-process
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/requirements-development-process
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-development-process-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams starting new projects often run ad-hoc requirements work that skips critical activities, producing incomplete specifications and expensive downstream defects. This Skill provides a structured six-phase workflow that coordinates elicitation, analysis, specification, and validation into one coherent process. ## Core Features & Use Cases - Six-Phase Lifecycle Orchestration: Guides foundation setup, elicitation, analysis and modeling, specification, validation, and iteration with explicit decision gates between phases. - Scaled Timeline Estimates: Provides phase-by-phase duration estimates for small, medium, and large projects (2 to 27 weeks) so the process fits the project size. - Sub-Skill Coordination: References 23 individual requirements engineering skills (use cases, decision tables, SRS writing, reviews) at the exact phase where each applies. - Use Case: A business analyst starting a chemical inventory system project uses the workflow to plan stakeholder interviews, build data and state models, write an SRS with acceptance criteria, run a formal walkthrough, and baseline 58 validated requirements in nine weeks. ## Quick Start Ask the agent to plan and run the complete requirements development process for your new project, starting with the vision and scope foundation phase.

Frequently Asked Questions about requirements-development-process

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

FAQPage Schema
How do I plan a requirements development process for a new project?▼

Start with the foundation phase: create a vision and scope document, analyze stakeholders, and draw a context diagram. Then run elicitation, analysis, specification, and validation as overlapping phases with decision gates, scaling each phase's duration to your project size.

How long does the requirements phase take for different project sizes?▼

Small projects under 50 requirements take about 2-3 weeks total, medium projects with 50-200 requirements take 7-14 weeks, and large projects over 200 requirements take 14-27 weeks. Elicitation, analysis, and specification overlap rather than running sequentially.

What elicitation techniques should I use for requirements gathering?▼

Combine stakeholder interviews for depth, observation to reveal unspoken workarounds, questionnaires to reach larger groups, and workshops to resolve cross-functional conflicts. The workflow includes a technique selector activity that matches methods to each stakeholder class.

Should requirements elicitation finish before analysis starts?▼

No. The workflow explicitly treats elicitation, analysis, and specification as overlapping phases. Starting analysis on early elicitation results surfaces gaps that redirect further elicitation, avoiding the delays and late discoveries of a strict waterfall sequence.

When should requirements be validated before baselining?▼

Validate after specification but before baseline, using formal reviews or walkthroughs, conceptual testing with scenarios, and prototype validation for UI requirements. The decision gate requires all critical and major defects resolved plus stakeholder approval before baselining.

What are common requirements process mistakes to avoid?▼

The documented anti-patterns are skipping the foundation phase, running phases strictly sequentially, skipping validation, ending BA involvement after baseline, and applying a one-size-fits-all process regardless of project size.