Forge-Requirements-Analysis

Evaluates, classifies, and validates software requirements before solution design begins.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-requirements-analysis-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Requirements-Analysis
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/01-Product/Forge-Requirements-Analysis
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-requirements-analysis-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Gathered requirements are often ambiguous, conflicting, or incomplete, leading teams to design solutions on unvalidated assumptions. This Skill structures the analysis of elicited requirements so they are clear, consistent, feasible, and traceable before engineering work starts. ## Core Features & Use Cases - Requirement Quality Assessment: Evaluates clarity, completeness, consistency, testability, and traceability of each requirement. - Classification & Structuring: Organizes requirements into functional, non-functional, and constraint categories with dependencies, risks, and assumptions documented. - Conflict & Gap Detection: Identifies contradictory expectations, undefined ownership, and open questions, escalating uncertainty to clarification workflows. - Use Case: A product team finishing stakeholder interviews uses this Skill to turn raw notes into a structured requirements specification with a readiness assessment, so architects can begin design with confidence. ## Quick Start Analyze the requirements in my project brief and produce a structured requirements specification with classifications, risks, and a readiness assessment.

Frequently Asked Questions about Forge-Requirements-Analysis

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

FAQPage Schema
How do I analyze software requirements before design?▼

Review each requirement for clarity, completeness, consistency, testability, and traceability, then classify them as functional, non-functional, or constraints. Document dependencies, risks, and assumptions, and produce a readiness assessment before design begins.

How to identify conflicting requirements in a project?▼

Look for contradictory expectations, competing priorities, impossible constraints, and undefined ownership across the requirement set. When conflicts are found, escalate them through a structured clarification process with stakeholders rather than resolving them unilaterally.

What is the difference between functional and non-functional requirements?▼

Functional requirements define system behavior such as user actions, workflows, and data processing. Non-functional requirements define quality expectations like performance, security, reliability, accessibility, and maintainability.

When should requirements analysis not be performed?▼

Skip formal analysis when no requirements exist yet, when the need is discovering stakeholder needs, or when the task is a simple implementation with clear acceptance criteria. Purely technical debugging also does not require it.

Does requirements analysis decide the technical architecture?▼

No. Requirements analysis assesses feasibility and prepares a validated baseline, but it does not define architecture, select technologies, or write code. Those decisions belong to downstream solution architecture activities.