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.

assetsconstraint-inventory.md

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

Constraint Inventory: [Project Name]

Real Constraints (Facts)

These are definitely true. Not negotiable.

Constraint Impact on Solution Source/Evidence
[constraint] [how it limits options] [why you know it's true]
[constraint] [impact] [source]
[constraint] [impact] [source]

Time Constraints

  • Available hours per week: [number]
  • Target completion: [date or "no deadline"]
  • Hard deadline (if any): [date and why]

Skill Constraints

  • Skills I have: [list]
  • Skills I'd need to learn: [list]
  • Skills explicitly avoiding: [list - things I won't learn for this]

Resource Constraints

  • Budget: [amount or "zero"]
  • Infrastructure available: [what exists]
  • Tools/services committed to: [if any]

Integration Constraints

  • Must work with: [existing systems, APIs, data sources]
  • Must NOT touch: [off-limits systems]

Assumptions (To Validate)

Things I believe are true but haven't confirmed.

Assumption If Wrong... How to Validate Status
[assumption] [consequence if false] [validation approach] Unvalidated / Validated / Invalidated
[assumption] [consequence] [approach]
[assumption] [consequence] [approach]

Risks (Pre-Mortem Results)

"It's 6 months later and this project failed. What happened?"

Failure Mode Probability Impact Mitigation
[how it could fail] H/M/L H/M/L [what reduces risk]
[failure mode]
[failure mode]

Top 3 Risks to Monitor

  1. [Risk] - Watch for: [early warning sign]
  2. [Risk] - Watch for: [early warning sign]
  3. [Risk] - Watch for: [early warning sign]

Dependencies

Things that must exist or happen before/during this project.

Dependency Type Status Blocker If Missing
[dependency] External / Internal / Learning Available / Pending / Unknown Yes / No
[dependency]

Validation

Before proceeding, confirm:

  • Time constraint is realistic (not aspirational)
  • At least 3 assumptions are identified
  • Pre-mortem identified non-obvious failure modes
  • Dependencies are listed with current status
  • Nothing is listed as "constraint" that's actually a preference

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.