gap-analysis
Gap Analysis
Systematically identify discrepancies between documented requirements, specifications, and actual implementation through comprehensive comparison, analysis, and gap identification to improve system completeness and accuracy.
When to use me
Use this skill when:
- Requirements documentation exists but implementation status is unclear
- Specifications have evolved but documentation hasn't been updated
- Code changes have been made without corresponding documentation updates
- Preparing for audits, compliance checks, or quality assessments
- Onboarding new team members who need accurate system understanding
- Planning refactoring or modernization efforts
- Validating that implementation matches design intentions
- Identifying technical debt in undocumented features
- Assessing risk from undocumented behavior
What I do
More from wojons/skills
adversarial-thinking
Apply systematic adversarial thinking patterns including devil's advocate, assumption busting, red teaming, and white hat security approaches
45devils-advocate
Challenge ideas, assumptions, and decisions by playing devil's advocate to identify weaknesses and prevent groupthink
41redteam
Think and act like an attacker to identify security vulnerabilities, weaknesses, and penetration vectors through adversarial security testing
37code-migration
Guide framework and library migrations with incremental strategies, breaking change analysis, compatibility testing, and automated migration tools
35observability-logging
Use logs as part of comprehensive observability strategy including metrics, traces, alerts, and dashboards for system understanding and operational excellence
34white-hat
Build defensive security capabilities, implement security by design, and practice ethical hacking to protect systems proactively
34