phase_02_requirements_scope

Convert a PRD into functional and non-functional requirements with a traceability matrix.

2|Updated Jan 14, 2026

Search Tags:#requirements #traceability #functional #stakeholders #non-functional #RTM #phase-2

Ready to run

npx skills add https://github.com/Harery/OCTALUME --skill phase-02-requirements-scope

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: phase_02_requirements_scope
Source: https://github.com/Harery/OCTALUME/tree/main/skills/phase_02_requirements_scope
Command: npx skills add https://github.com/Harery/OCTALUME --skill phase-02-requirements-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 2 of the OCTALUME lifecycle often stalls teams by translating a high-level PRD into detailed, actionable requirements. This Skill ensures that vision becomes buildable through a structured requirements specification, a complete RTM, and explicit validation criteria.

Core Features & Use Cases

Elicitation and workshop facilitation to derive functional and non-functional requirements.
Creation of a Traceability Matrix linking PRD items to requirements, tests, and design.
Definition of data requirements, security and compliance considerations, and acceptance criteria.
Output ready artifacts for Phase 3 architecture design, including a Functional Requirements Spec, Non-Functional Requirements, and RTM.

Quick Start

Provide your PRD as input and run the Phase 2 workflow to generate a Functional Requirements Specification, Non-Functional Requirements, Security & Compliance mappings, and a Requirements Traceability Matrix ready for Phase 3 architecture design.

Frequently Asked Questions about phase_02_requirements_scope

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

FAQPage Schema

How do I convert a PRD into testable functional requirements?▼

To convert a PRD into testable functional requirements, the Skill processes your PRD to output a structured specification defining validation criteria and readiness for architecture design.

What is a requirements traceability matrix and how is it generated from a PRD?▼

A requirements traceability matrix links PRD items to tests and design. It is generated by mapping elicited functional and non-functional requirements to their corresponding validation criteria.

How do I map security and compliance considerations during requirements elicitation?▼

You map security and compliance considerations by defining data requirements and acceptance criteria alongside functional requirements, outputting explicit mappings for downstream architecture design.

Can I define non-functional requirements directly from a product vision document?▼

Yes, you can define non-functional requirements from a product vision by translating the PRD into detailed specifications that include data, security, and compliance considerations.

What is the best way to prepare requirements for Phase 3 architecture design?▼

The best way to prepare requirements for Phase 3 architecture is to generate a complete requirements traceability matrix and functional specifications that explicitly define validation criteria.