mcpField
P
plan-gap-analysis

plan-gap-analysis

github.com/d-o-hubTesting & quality1341 installsUpdated today
Repository

About plan-gap-analysis

plan-gap-analysis is a skill for developers comparing project plans with implemented code. It inventories documents and source files, prioritizes discrepancies by severity, and produces actionable TODOs with file references.

Key features

  1. 01Inventory plan documents and source files
  2. 02Check requirements by project phase
  3. 03Identify and prioritize implementation gaps
  4. 04Generate TODOs with file references

Use cases

  1. 01Compare architecture plans with code
  2. 02Review security requirements and test coverage
  3. 03Organize outstanding implementation work

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/d-o-hub/rust-self-learning-memory --skill plan-gap-analysis

After installing, type/plan-gap-analysisin Claude Code to confirm it loaded.

Details

From the project README

Plan Gap Analysis

Analyze gaps between documented plans in plans/ and actual implementation.

Workflow

Phase 1: Plan Inventory

Read all plan files:

  • 00-overview.md - Project summary and metrics
  • 01-understand.md - Requirements and components
  • 02-plan.md - Architecture decisions and roadmap
  • 03-execute.md - Implementation details
  • 04-review.md - Quality requirements
  • 05-secure.md - Security requirements
  • 06-feedback-loop.md - Refinements
Phase 2: Codebase Inventory
# List all crates
find . -name "Cargo.toml" -not -path "*/target/*"

# List source files
find . -name "*.rs" -not -path "*/target/*"

Crates to analyze:

  • do-memory-core - Core data structures and orchestration
  • do-memory-storage-turso - Turso/libSQL backend
  • do-memory-storage-redb - redb cache layer
  • do-memory-mcp - MCP server and sandbox
  • do-memory-test-utils - Test utilities
  • benches - Performance benchmarks
Phase 3: Gap Identification

Check each phase:

PhaseFocus Areas
UNDERSTANDData structures, type definitions
PLANArchitectural decisions, success metrics
EXECUTEStorage, learning, MCP features
REVIEWFR1-FR7, NFR1-NFR6 tests
SECUREAttack surfaces, mitigations
FEEDBACKEdge cases, optimizations
Phase 4: Prioritization

Critical (Blocks production):

  • Security vulnerabilities
  • Data corruption risks
  • Missing core functionality

High (Affects quality):

  • Performance targets not met
  • Test coverage below target
  • Missing error handling

Medium (Technical debt):

  • Code quality issues
  • Documentation gaps
Phase 5: TODO Generation
## Phase [N]: [NAME]

### Critical Priority
- [ ] [Component] - [Missing item]
  - File: path/to/file.rs
  - Plan: plans/0X-phase.md:LineNumber
  - Impact: [Description]
  - Effort: [Estimate]

Output Format

# Plan Gap Analysis Report
**Total Requirements**: X
**Implemented**: Y (Z%)
**Gaps Identified**: N

## By Phase
- Phase 1: X/Y complete
- Phase 2: X/Y complete
- ...

## Critical Gaps
1. [Gap] - Priority, Effort

Best Practices

✓ Be systematic: Check every requirement ✓ Be specific: Reference exact file locations ✓ Be accurate: Verify, don't assume ✓ Be prioritized: Critical > High > Medium > Low ✓ Be actionable: Include file paths and estimates

Comments

Markdown supported