requirements-analysis
Diagnose requirements problems and guide discovery of real needs instead of premature solutions.
- Identifies five distinct requirements states (no problem statement, solution-first thinking, vague needs, hidden constraints, scope creep) with specific symptoms, key questions, and interventions for each
- Helps distinguish stated wants from underlying problems through problem archaeology, Jobs-to-be-Done interviews, and constraint inventory exercises
- Produces persistent artifacts (Problem Statement Brief, Need Hierarchy, Constraint Inventory, Scope Definition) that hand off to system-design skill when validated
- Prevents common anti-patterns like solution specification, stakeholder fiction, infinite backlogs, and feature transplants through structured questioning and health checks
Requirements Analysis: From Vague Intent to Validated Needs
You diagnose requirements-level problems in software projects. Your role is to help solo developers distinguish stated wants from underlying problems, discover real constraints, and avoid premature solution thinking.
Core Principle
Requirements are hypotheses about what will solve a problem. The goal is not to document requirements but to discover whether they address the actual problem.
The States
State RA0: No Problem Statement
Symptoms:
- Starting with "I want to build X" (solution, not problem)
- Can't articulate who has what problem
- "Everyone needs this" reasoning
- Feature list without problem grounding
- Copying existing solutions without understanding why they exist
More from jwynia/agent-skills
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Provides analysis tools for auditing existing designs and generation tools for creating color palettes, typography systems, design tokens, and component templates. Supports React, Vue, Svelte, and vanilla HTML/CSS. Use when building web components, pages, or applications. Keywords: design, UI, frontend, CSS, components, palette, typography, tokens, accessibility.
2.1Kgodot-best-practices
Guide AI agents through Godot 4.x GDScript coding best practices including scene organization, signals, resources, state machines, and performance optimization. This skill should be used when generating GDScript code, creating Godot scenes, designing game architecture, implementing state machines, object pooling, save/load systems, or when the user asks about Godot patterns, node structure, or GDScript standards. Keywords: godot, gdscript, game development, signals, resources, scenes, nodes, state machine, object pooling, save system, autoload, export, type hints.
1.5Kpresentation-design
Design and evaluate presentations that communicate effectively. Use when designing a presentation, creating slides, getting presentation feedback, structuring a talk, or reviewing slides. Keywords: presentation, slides, talk, PowerPoint, Keynote, reveal.js.
1.4Kweb-search-tavily
Search the web using Tavily API for high-quality, AI-optimized results with advanced filtering options. Use when you need structured search results, domain filtering, relevance scores, or AI-generated answer summaries. Requires TAVILY_API_KEY. Keywords: tavily, advanced search, filtered search, domain filtering, relevance scoring.
1.1Kpdf-generator
Create and manipulate PDF files programmatically. Use when the user needs to generate PDFs, fill PDF forms, extract PDF content, add watermarks/overlays, or merge documents. Supports both template-based generation (form filling, overlays) and from-scratch creation. Keywords: PDF, document, form, fillable, merge, watermark, extract, text, report.
728story-coach
Act as an assistive writing coach who guides but never writes for the user. Use when helping someone develop their own writing through questions, diagnosis, and frameworks. Critical constraint - never generate story prose, dialogue, or narrative content. Instead ask questions, identify issues, suggest approaches, and let the writer write.
712