skills.rest
NexusSema
NexusSemaOFFICIAL
Explore all skills by this author →
GitHub

epics/gaps-analysis

Map PRD, architecture, epics, and UX references to surface gaps and produce a prioritized remediation plan.

5|3|Updated Mar 4, 2026
Search Tags:#architecture#dependencies#remediation#epics#traceability#gap-analysis#planning-artifacts
One-click install
npx skills add https://github.com/NexusSema/omg-marketplace --skill epics-gaps-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epics/gaps-analysis
Source: https://github.com/NexusSema/omg-marketplace/tree/main/plugins/sdlc/skills/epics/gaps-analysis
Command: npx skills add https://github.com/NexusSema/omg-marketplace --skill epics-gaps-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Gaps between architecture decisions, planning artifacts, and implementation stories often derail projects. This skill discovers missing infrastructure, undeclared dependencies, implicit assumptions, and incomplete traceability that block development.

Core Features & Use Cases

  • Gap discovery & cataloging: surface gaps across PRD, architecture, epics, and UX specs.
  • Dependency & ordering insights: reveal hidden dependencies and sequencing risks.
  • Remediation planning: propose concrete stories/epics to close gaps before sprint planning.

Quick Start

Run the gaps-analysis workflow against your planning artifacts to surface architecture-to-story gaps and get a prioritized remediation plan.

Frequently Asked Questions about epics/gaps-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is gap analysis in software epics and planning artifacts?▼

Gap analysis in software epics discovers missing infrastructure, undeclared dependencies, and incomplete traceability between your PRD, architecture, and UX design, preventing development blockers before coding begins.

How do I find hidden dependencies between architecture decisions and implementation stories?▼

To find hidden dependencies, map all references across PRD, architecture, epics, and UX design to reveal implicit dependencies, missing prerequisites, and sequencing risks blocking your implementation stories.

How do I create a remediation plan for missing prerequisites in sprint planning?▼

Create a remediation plan by cataloging gaps across your planning artifacts and proposing concrete, prioritized stories and epics to close those missing prerequisites before sprint planning begins.

Can I trace requirements from PRD to epics to uncover implicit assumptions?▼

Yes, you can trace requirements by mapping references across PRD, architecture, epics, and UX specs to surface implicit assumptions and incomplete traceability that could derail your development.

What is the best way to surface architecture-to-story gaps before development?▼

The best way to surface architecture-to-story gaps is running a gaps-analysis workflow against your planning artifacts to reveal missing infrastructure and produce a prioritized remediation plan.

Related Skills

Explore More Product & Management Skills→
gaiastudio-aigaiastudio-ai
2

gaia-document-rulesets

Validate Gaia planning documents with two-pass frontmatter and structural checks.

Official
Advanced
shalevaminshalevamin

sprint-plan

Estimate team capacity, select stories, map dependencies, and identify risks for sprint planning.

Community
Intermediate
salazarsebassalazarsebas
9

create-epics-and-stories

Decompose product requirements into epics and stories with acceptance criteria.

Community
Advanced
Alexander-M-DickersonAlexander-M-Dickerson
58

audit-math

Audit LaTeX math sections for inconsistencies and cross-reference gaps.

Community
Advanced