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.

assetsneed-hierarchy.md

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

Need Hierarchy: [Project Name]

Core Needs (Must Have)

These are essential. Without them, the problem isn't solved.

Need 1: [Need description - start with verb]

Why essential: [What fails if this is missing] Derived from: [Which part of the problem statement] Testable by: [How you'd verify this need is satisfied] Minimum viable: [Smallest implementation that satisfies]

Need 2: [Need description]

Why essential: Derived from: Testable by: Minimum viable:

Need 3: [Need description]

Why essential: Derived from: Testable by: Minimum viable:

Supporting Needs (Should Have)

These significantly improve the solution but aren't essential for V1.

Need: [Need description]

Why valuable: [What it adds] Depends on: [Which core need must exist first] Defer trigger: [What would make this become Must Have]

Need: [Need description]

Why valuable: Depends on: Defer trigger:

Enhancement Needs (Could Have)

Nice to have if time permits. Won't delay V1.

Need: [Need description]

Value if included: [What it adds] Why deferrable: [Why this can wait]

Explicitly Deferred (Won't Have in V1)

Acknowledged as potentially valuable but consciously excluded.

Need: [Need description]

Why deferred: [Reason for exclusion] Reconsider when: [Trigger for bringing this back]

Need: [Need description]

Why deferred: Reconsider when:

Validation

Before proceeding, confirm:

  • Each need starts with a verb (action, not thing)
  • No need contains implementation/technology words
  • Core needs are genuinely essential (would you ship without them?)
  • Each need traces back to problem statement
  • Each need has testable acceptance criteria
  • At least one thing is in "Won't Have"

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.