Analyze requirements for completeness, missing areas, and gaps. Uses domain checklists, NFR categories, and INVEST criteria to identify what's missing from elicited requirements.
Analyzes requirements for completeness using INVEST criteria, NFR checklists, and domain categories. Use when requirements are elicited to identify missing functional/non-functional areas before specification.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install requirements-elicitation@melodic-softwareThis skill is limited to using the following tools:
Analyze requirements for completeness and identify missing areas.
Keywords: gap analysis, completeness, missing requirements, coverage, validation, INVEST, NFR check, requirement gaps
Invoke this skill when:
Check coverage across standard requirement categories:
categories:
functional:
- user_management
- data_management
- processing
- integration
- reporting
- notifications
non_functional:
- performance
- security
- usability
- reliability
- scalability
- maintainability
- accessibility
constraints:
- technical
- business
- regulatory
- resource
- timeline
assumptions:
- environmental
- user_behavior
- dependencies
Ensure non-functional requirements are specified:
nfr_checklist:
performance:
- response_time_defined: false
- throughput_defined: false
- capacity_defined: false
security:
- authentication_specified: false
- authorization_specified: false
- data_protection_specified: false
usability:
- accessibility_considered: false
- learning_curve_addressed: false
- error_handling_defined: false
reliability:
- uptime_target_set: false
- error_recovery_defined: false
- backup_strategy_specified: false
scalability:
- growth_projection_defined: false
- scaling_strategy_specified: false
Evaluate requirements against INVEST:
invest_criteria:
independent:
description: "Requirement can be developed independently"
check: "Are there circular dependencies?"
negotiable:
description: "Details can be negotiated"
check: "Is the requirement too prescriptive?"
valuable:
description: "Delivers value to stakeholders"
check: "Is the business value clear?"
estimable:
description: "Can be estimated for effort"
check: "Is scope clear enough to estimate?"
small:
description: "Can be completed in a sprint"
check: "Is the requirement too large?"
testable:
description: "Can be verified when implemented"
check: "Are acceptance criteria defined?"
Apply domain-appropriate checklists:
domain_checklists:
e-commerce:
- product_catalog
- shopping_cart
- checkout
- payment
- order_management
- inventory
- shipping
- returns
authentication:
- login
- registration
- password_reset
- session_management
- mfa
- sso
- permissions
reporting:
- data_sources
- filters
- visualizations
- export
- scheduling
- access_control
Read existing requirements from:
.requirements/{domain}/ folderFor each checklist:
gap_severity:
critical:
definition: "Requirement area essential for system viability"
examples: ["No security requirements", "No data validation"]
action: "Must address before proceeding"
major:
definition: "Significant gap that affects quality"
examples: ["No performance targets", "No error handling"]
action: "Should address soon"
minor:
definition: "Nice to have, not essential"
examples: ["No accessibility beyond basic", "Limited internationalization"]
action: "Address if time permits"
For each gap:
gap_analysis:
session_id: "GAP-{timestamp}"
domain: "{domain}"
analyzed_date: "{ISO-8601}"
requirements_analyzed:
total: {number}
from_interviews: {number}
from_documents: {number}
from_simulations: {number}
coverage_summary:
functional: 80%
non_functional: 45%
constraints: 60%
assumptions: 30%
gaps_identified:
critical:
- category: security
gap: "No authentication requirements"
recommendation: "Interview security stakeholder or run simulation"
suggested_technique: interview
major:
- category: performance
gap: "No response time targets"
recommendation: "Define SLAs with business stakeholder"
suggested_technique: interview
minor:
- category: accessibility
gap: "Only basic WCAG coverage"
recommendation: "Consider WCAG 2.1 AA compliance"
suggested_technique: domain-research
nfr_coverage:
performance: partial
security: missing
usability: covered
reliability: partial
scalability: missing
invest_assessment:
independent: 85%
negotiable: 90%
valuable: 95%
estimable: 70%
small: 75%
testable: 60%
recommendations:
- priority: high
action: "Conduct security-focused interview"
gaps_addressed: [security, authentication, authorization]
- priority: medium
action: "Define performance SLAs"
gaps_addressed: [performance, scalability]
ready_for_specification: false
blocker_gaps: [security, authentication]
Common functional gaps:
Common NFR gaps:
Common constraint gaps:
Common assumption gaps:
For filling gaps, delegate to:
Save gap analysis to:
.requirements/{domain}/analysis/GAP-{timestamp}.yaml
elicitation-methodology - Parent hub skillinterview-conducting - Fill gaps via interviewsstakeholder-simulation - Fill gaps via simulationdomain-research - Research domain requirementsCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.