skills.rest
shirogin
shiroginCOMMUNITY
Explore all skills by this author →
GitHub

problem-based-srs

Coordinate the Problem-Based SRS workflow from CP to FR/NFR with traceability.

1|Updated Mar 31, 2026
Search Tags:#traceability#srs#stakeholders#requirements-engineering#problem-based-srs#zigzag-validator
One-click install
npx skills add https://github.com/shirogin/jesuph-skills --skill problem-based-srs-shirogin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: problem-based-srs
Source: https://github.com/shirogin/jesuph-skills/tree/main/.agents/skills/problem-based-srs
Command: npx skills add https://github.com/shirogin/jesuph-skills --skill problem-based-srs-shirogin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Problem-Based SRS orchestrator enables teams to perform structured requirements engineering that traces every requirement back to a business problem, spanning CP, CN, SV, FR, and NFR artifacts.

Core Features & Use Cases

  • End-to-end orchestration from CP through CN, SV, FR/NFR with explicit traceability to business problems.
  • Integrated validation via zigzag-validator to ensure consistency across CP→CN→FR/NFR.
  • Clear guidance and saving conventions, with example references to best-practice artifacts.

Quick Start

Choose your artifact save location and start with Step 0 using the business-context skill to create and save the initial artifacts.

Frequently Asked Questions about problem-based-srs

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

FAQPage Schema
How do I ensure traceability from business problems to software requirements?▼

Problem-based SRS coordinates a structured requirements engineering workflow that traces every FR and NFR back to its originating business problem across CP, CN, and SV artifacts.

What is the best way to validate consistency across customer problems and functional requirements?▼

The best way to validate consistency across customer problems and functional requirements is using an integrated zigzag-validator that checks alignment throughout the CP to CN to FR/NFR generation process.

How do I start requirements engineering when I only have customer problems?▼

Starting requirements engineering from customer problems involves establishing an initial business context, then advancing through stakeholder viewpoints to generate functional and non-functional requirements.

Can I use this approach for projects starting with software-glance artifacts?▼

Yes, you can apply this workflow to projects starting with CPs and software-glance artifacts, advancing them through stakeholder viewpoints to systematically generate your FR and NFR artifacts.

Does this requirements engineering workflow support saving intermediate artifacts?▼

Yes, this requirements engineering workflow supports artifact saving conventions, providing clear guidance and example references to best-practice artifacts throughout the end-to-end orchestration.

When should I not use a problem-based SRS approach?▼

You should avoid a problem-based SRS approach if your project lacks initial customer problems or business context artifacts, as the workflow depends on advancing from these specific inputs.

Related Skills

Explore More Product & Management Skills→
shiroginshirogin
1

customer-problems

Identify and document Customer Problems from Step 0 business context using Subject-Verb format with penalties and classifications.

Community
Intermediate
ravenoakravenoak

ci-merge-gate

Automate CI merge-gate checks enforcing FR-0.2 and NFR-O1 compliance during pull requests.

Community
Intermediate
RafaelGorskiRafaelGorski
30

problem-based-srs

Guide a 5-step SRS methodology linking requirements to business problems.

Community
Advanced
drvossdrvoss
42

product-capability

Translate product requirements into testable capability specifications with acceptance criteria and traceability.

Community
Intermediate