promo-gap-analyzer

To identify promotion gaps, map your Jira and GitHub achievement signals against your organization's ladder criteria to reveal readiness gaps. This process cross-references evidence from multiple platforms to output a structured gap analysis with cited findings and actionable work plans.

Evidence-based gap analysis works by mapping your achievement signals from Confluence, Slack, and incident records to specific ladder criteria dimensions. It surfaces strengths and gaps with concrete citations, ensuring your promotion planning is grounded in real evidence rather than subjective vibes.

You can use GitHub and GitLab commit history to prove readiness by mapping that codebase evidence directly to your target level's ladder criteria. The analysis aggregates version control contributions alongside Jira tickets and Confluence docs to generate a cited, per-dimension readiness assessment.

The best way to map incident records to ladder criteria is to analyze those records against your current and target level requirements for the active review period. Cross-referencing incident data with Jira and Slack outputs a structured gap analysis highlighting readiness gaps with cited evidence.

You need to provide your current level, target level, and review period to generate a per-dimension promotion gap analysis. The analysis then aggregates evidence from platforms like GitHub, Jira, and Confluence to output cited findings, caveats, and actionable work for closing gaps.

Gap analysis output includes actionable work plans and caveats to guide conversations with managers and mentors. It provides a structured per-dimension breakdown with cited evidence from Jira and GitHub, ensuring you know exactly what work is needed to close identified readiness gaps.