Extract and summarize core features, constraints, and priorities from requirement documents. Use when analyzing PRDs, RFCs, business requirements, user stories, epics, or any requirement documentation to identify must-have features, technical constraints, priority levels (P0/P1/P2/MoSCoW), and key decision points. Triggers when users ask to summarize, analyze, extract, or understand requirements from documents.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/requirement-summarizer/SKILL.mdExtract and organize the essential information from requirement documents into a structured markdown summary that highlights core features, constraints, and priorities.
Follow these steps to summarize requirement documents:
First, read the entire requirement document to understand its structure and content:
Systematically identify and extract:
Core Features:
Constraints:
Priorities:
Create a markdown report with the following structure:
# Requirements Summary: [Document Name]
## Document Metadata
- **Source**: [Document title/filename]
- **Type**: [PRD/RFC/User Story/Business Requirement/etc.]
- **Date Analyzed**: [Current date]
## Executive Summary
[2-3 sentence overview of what this requirement document defines]
## Core Features
### [Feature Category 1]
- **[Feature Name]**: [Brief description]
- Priority: [P0/P1/P2 or Must/Should/Could]
- Notes: [Any relevant context]
### [Feature Category 2]
...
## Constraints
### Technical Constraints
- [Constraint description]
- [Constraint description]
### Business Constraints
- [Constraint description]
- [Constraint description]
### Compliance/Regulatory Constraints
- [Constraint description]
### Performance Constraints
- [Constraint description]
## Priority Breakdown
### Critical/Must-Have (P0)
1. [Feature/requirement]
2. [Feature/requirement]
### High Priority/Should-Have (P1)
1. [Feature/requirement]
2. [Feature/requirement]
### Medium Priority/Could-Have (P2)
1. [Feature/requirement]
2. [Feature/requirement]
### Future/Won't-Have (P3)
1. [Feature/requirement]
## Key Decisions & Open Questions
- **Decision**: [What needs to be decided]
- Options: [If applicable]
- Impact: [Why this matters]
- **Open Question**: [Unclear requirement or missing information]
## Success Criteria
[How will we know this is successful? Metrics, acceptance criteria, or outcomes]
## Dependencies
- [External dependencies or prerequisites]
- [Related systems or teams]
## Timeline & Milestones
- [Key dates if mentioned in requirements]
- [Phase breakdown if applicable]Before presenting the summary, verify:
Multiple conflicting priorities:
Implicit vs explicit priorities:
Vague or ambiguous requirements:
Missing information:
Be concise but comprehensive:
Maintain objectivity:
Prioritize based on evidence:
Adapt to document type:
Handle different priority systems:
User request:
"Summarize the requirements from this PRD and identify what's critical for the first release"
Response approach:
User request:
"What are the main features and constraints in these user stories?"
Response approach:
ArabelaTso/Skills-4-SE
4f38503
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.