Validate WCAG 2.1 Level AA compliance and accessibility best practices. Use when performing accessibility audits and WCAG certification.
The English summary is being prepared. Showing the original description.
Analyze feature requirements, dependencies, and security considerations. Use when starting feature implementation from GitHub issues to understand scope, technical feasibility, and risks.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
This skill provides systematic analysis of feature requirements from GitHub issues, evaluating technical feasibility, dependencies, security implications, and implementation scope.
From GitHub Issue:
Deliverable: Structured requirements list with priorities
Assess Technology Fit:
Tools to Use:
scripts/analyze_deps.py for dependency analysisDeliverable: Technology recommendations with rationale
Identify Dependencies:
Check for Conflicts:
# Use the analyze_deps script
python scripts/analyze_deps.py --feature <feature-name>
Deliverable: Dependency map with conflict analysis
Review Security Implications:
Use Checklist:
Refer to security-checklist.md for systematic review
Deliverable: Security risk assessment and mitigation plan
Define Boundaries:
Estimate Complexity:
Deliverable: Scope statement with effort estimate
Create an analysis report with:
# Feature Analysis: [Feature Name]
## Requirements Summary
- [ ] Requirement 1
- [ ] Requirement 2
...
## Technical Approach
**Recommended Stack:** Python 3.9+, pytest, pydantic
**Key Libraries:** [list]
**Architecture Pattern:** [pattern]
## Dependencies
**External:**
- package-name==version (reason)
**Internal:**
- module.submodule (reason)
## Security Considerations
**Risk Level:** Low/Medium/High
**Key Concerns:**
- [concern 1]: [mitigation]
## Scope
**In Scope:**
- [feature 1]
**Out of Scope:**
- [deferred item]
**Effort Estimate:** [hours/days]
## Recommendations
1. [Recommendation 1]
2. [Recommendation 2]
Requirements Analysis:
Technical Evaluation:
Security First:
Scope Management:
# 1. Fetch issue details
Use mcp__github-mcp__get_issue to retrieve issue #<number>
# 2. Review requirements
Work through requirements-checklist.md systematically
# 3. Analyze dependencies
python scripts/analyze_deps.py --feature feature-name
# 4. Security review
Complete security-checklist.md
# 5. Generate analysis report
Create report in docs/implementation/feature-name-analysis.md
Input: GitHub issue number Process: Systematic analysis using checklists and scripts Output: Analysis report + recommendations Next Step: Design skill for architecture planning
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Validate WCAG 2.1 Level AA compliance and accessibility best practices. Use when performing accessibility audits and WCAG certification.
The English summary is being prepared. Showing the original description.
Run SQL queries against psql, BigQuery, or MySQL from the terminal, including natural-language-to-SQL and schema exploration. Use when analyzing data, inspecting DB state, or debugging tables. Trigger on "query the database", "SQL", "show me data from", "explore table".
The English summary is being prepared. Showing the original description.
Design REST APIs or function contracts with clear request/response specifications, error handling patterns, authentication strategies, and comprehensive documentation.
The English summary is being prepared. Showing the original description.
Generate comprehensive API endpoint tests for REST and GraphQL APIs. Creates tests for all HTTP methods, status codes, authentication, and validation.
The English summary is being prepared. Showing the original description.
Design component architecture and module structure using established architectural patterns for clean, maintainable, and scalable systems.
The English summary is being prepared. Showing the original description.
Generate CHANGELOG entries following conventional commits format with semantic versioning. Use when finalizing features to maintain proper change history.
The English summary is being prepared. Showing the original description.