skilld
All skills
jwynia avatar

/requirements-analysis

@6ac6c30
by J Wyniajwynia/agent-skills160 stars
20

Diagnose requirements problems and guide discovery of real needs and constraints

Ask your Agent

Use this Skill: https://skilld.dev/gh/jwynia/agent-skills/requirements-analysis

This session only. Nothing lands on disk.

assetsproblem-statement.md

≈321 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Problem Statement: [Project Name]

The Problem

[One paragraph: Who has what problem, and what happens because of it. No solutions, only problems.]

Who: [Specific person or role - "I" is valid for solo projects] Problem: [What's wrong, frustrating, or missing] Impact: [What happens because of this problem]

Current State

[How is this being handled today? What's the workaround, even if it's "suffer through it"?]

Current approach: Why it's insufficient:

Why Now

[What triggered this? What's changed that makes this worth solving now?]

Success Looks Like

[How would you know the problem is solved? Be specific enough to test.]

  • [Concrete success indicator 1]
  • [Concrete success indicator 2]
  • [Concrete success indicator 3]

Not Trying to Solve

[Explicitly out of scope - problems that might seem related but aren't being addressed]

  • [Related problem we're NOT solving]
  • [Adjacent problem we're NOT solving]

Validation

Before proceeding, confirm:

  • Problem statement contains no solution words (no technology, no features)
  • "Who" is specific (not "users" or "everyone")
  • Impact is real and felt (not theoretical)
  • Success criteria are testable
  • At least one thing is explicitly out of scope

Source: SKILL.md on GitHub

Third-party checks

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    A diagnostic skill for software requirements analysis that helps developers define problems and constraints using templates and interviews. No malicious code, risky dependencies, or suspicious network operations were detected.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    4/4 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 6ac6c30. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Dormantupdated 8 months ago

Capability

Other metadata
metadata
{
  "author": "jwynia",
  "version": "1.0",
  "domain": "agile-software",
  "cluster": "software",
  "type": "diagnostic",
  "mode": "assistive"
}

Topics

  • requirements
  • discovery
  • problem-analysis
  • agile
  • scope
  • constraints
  • diagnostic
  • software-planning
  • solo-developer

README badge

README badge for jwynia/agent-skills/requirements-analysis

What it does

Diagnoses requirements problems in software projects by helping developers distinguish stated wants from underlying problems, discover real constraints, and avoid solution-first thinking. Walks through five diagnostic states from "no problem statement" through "validated requirements," using targeted questions and exercises like Jobs-to-be-Done interviews, constraint inventories, and scope prioritization to move requirements from vague to testable.

Generated from the current SKILL.md.

Frequently asked

Does this skill help me write code or choose technologies?
No. This skill diagnoses requirements problems and guides discovery of real needs and constraints. Technology selection and implementation belong to the system-design skill.
What if I'm a solo developer building for myself?
Be honest about your own needs instead of inventing users. The skill includes questions to ground your requirements in actual frustration, not assumptions.
Can I skip states if I think my requirements are already clear?
No. The skill requires starting at the earliest problem state present. If RA0 symptoms exist (no problem statement), you must work through that before moving to clarifying needs.
What does this skill produce that I can hand off to other agents?
A Validated Requirements Document with a clear problem statement, testable needs, explicit constraints, and a bounded V1 scope ready for handoff to the system-design skill.
Does this work for existing projects or only new ones?
Both. The skill can diagnose requirements problems in ongoing projects to surface hidden constraints, scope creep, or solution-first thinking that's causing issues.

Generated from the current SKILL.md. These answers refresh after source changes.