requirements-analysis
Helps gather requirements and produce a structured task document following a project-specific template.
Install
mkdir -p .claude/skills/requirements-analysis-matrixfounder && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13808" && unzip -o skill.zip -d .claude/skills/requirements-analysis-matrixfounder && rm skill.zipInstalls to .claude/skills/requirements-analysis-matrixfounder
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when gathering and refining requirements into a structured TASK.Key capabilities
- →Identify use cases, actors, and preconditions for a project
- →List open questions about requirements
- →Describe every step in scenarios
- →Consider errors, exceptions, and boundary conditions
- →Use existing terminology from project documentation
- →Link new functionality with existing functionality
How it works
The skill follows an analysis loop to identify use cases, actors, and preconditions, then clarifies open questions. It structures findings into a technical specification by detailing scenarios and considering edge cases.
Inputs & outputs
When to use requirements-analysis
- →Analyzing user requirements
- →Creating technical task specification
- →Identifying project edge cases
About this skill
Requirements Analysis
1. Analysis Loop
- Reconnaissance: Read project structure,
.AGENTS.md. - Identification: What are the use cases? Actors? Preconditions?
- Clarification: List open questions. Better to ask now than fail later.
2. Technical Specification (TASK) Structure
You MUST follow the structure defined in assets/task_template.md.
Read this file to understand the required headers and sections.
3. Important Rules
✅ DO:
- Be detailed: Describe every step in scenarios.
- Think about edge cases: Consider errors, exceptions, boundary conditions.
- Ask questions: If something is unclear — add to "Open Questions".
- Use existing terminology: Use terms from project documentation.
- Link to existing functionality: Explicitly state how new functionality interacts with existing.
❌ DO NOT:
- DO NOT write code: You create TASK, not implementation.
- DO NOT design architecture: This is the Architect's task.
- DO NOT invent: If unclear, ask a question.
- DO NOT make assumptions: Explicitly state where you make an assumption.
- DO NOT overcomplicate: Keep it simple, don't overengineer.
- DO NOT ignore existing functionality: Study the project before writing TASK.
- DO NOT leave important decisions for later: All key decisions must be selected or clarification requested from user.
🔴 CRITICAL: Uncertainty Management
You are at the earliest stage of development. Unresolved uncertainty now can lead to project failure. Therefore:
- Pay maximum attention to unclear points
- Do not hesitate to ask many questions
- Better to ask a "stupid" question than make an incorrect assumption
- If in doubt — add to "Open Questions"
When not to use it
- →When the task is to write code
- →When the task is to design architecture
- →When the task involves inventing details if unclear
Limitations
- →The skill does not write code
- →The skill does not design architecture
- →The skill does not invent information
How it compares
This skill provides a structured analysis loop and a predefined task template, unlike a manual approach that might lack a systematic way to identify and document requirements and edge cases.
Compared to similar skills
requirements-analysis side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| requirements-analysis (this skill) | 0 | 6mo | No flags | Intermediate |
| pmbok-project-management | 38 | 9mo | No flags | Intermediate |
| project-planner | 32 | 9mo | Review | Intermediate |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by MatrixFounder
View all by MatrixFounder →You might also like
pmbok-project-management
jgtolentino
Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
planning-agent
parcadei
Planning agent that creates implementation plans and handoffs from conversation context
pdd
mikeyobrien
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.