AgentSkillsCN

gap-analysis

指导用户对 AG3NT 进行差距分析,识别缺失功能、评估实施进度,并合理规划优先级。

SKILL.md
--- frontmatter
name: gap-analysis
description: Guide to performing gap analysis on AG3NT, identifying missing features, assessing implementation status, and prioritizing work.
version: "1.0.0"
tags:
  - analysis
  - planning
  - prioritization
  - review
triggers:
  - "gap analysis"
  - "what's missing"
  - "implementation status"
  - "feature gaps"
  - "prioritize work"
required_permissions: []
license: MIT
compatibility: AG3NT 1.x
metadata:
  author: ag3nt-team
  category: development

Gap Analysis Guide

Use this skill when assessing AG3NT's implementation status, identifying missing features, or prioritizing development work.

Gap Analysis Process

code
┌──────────────────────────────────────────────────────────────┐
│                    GAP ANALYSIS WORKFLOW                     │
├──────────────────────────────────────────────────────────────┤
│                                                              │
│  1. GATHER REQUIREMENTS                                      │
│     ├── Read PRD: /docs/AG3NT_Product_Requirements_*.md     │
│     ├── Read Architecture: /docs/AG3NT_System_Architecture_*│
│     └── Note all "Required" features                         │
│                                                              │
│  2. ASSESS CURRENT STATE                                     │
│     ├── Check each component's implementation                │
│     ├── Run tests to verify functionality                    │
│     └── Document status: ✅ Complete, ⚠️ Partial, ❌ Missing │
│                                                              │
│  3. IDENTIFY GAPS                                            │
│     ├── Compare requirements vs. implementation              │
│     ├── Note blocking dependencies                           │
│     └── Estimate effort for each gap                         │
│                                                              │
│  4. PRIORITIZE                                               │
│     ├── HIGH: Blocks core use cases                          │
│     ├── MEDIUM: Enhances capabilities                        │
│     └── LOW: Nice to have                                    │
│                                                              │
│  5. CREATE ACTION PLAN                                       │
│     └── Assign gaps to sprints based on priority             │
│                                                              │
└──────────────────────────────────────────────────────────────┘

Current Implementation Status

Core Components

ComponentStatusCompletionNotes
Gateway Core✅ Stable95%HTTP, WS, routing
Agent Worker✅ Stable85%LLM, tools, memory
Control Panel✅ Complete95%Web UI
TUI✅ Complete90%Terminal interface
Multi-Model✅ Complete100%5 providers
Skill System✅ Complete100%Discovery, execution
Multi-Node✅ Complete100%Companion nodes
Agent Tools⚠️ Gap70%Some tools missing
Tests⚠️ Gap40%Coverage target: 80%

Channel Status

ChannelStatusPriority
CLI✅ Complete-
Telegram✅ Complete-
Discord✅ Complete-
Slack✅ Complete-
WhatsApp❌ MissingHIGH
Signal❌ MissingHIGH
iMessage❌ MissingMEDIUM
Teams❌ MissingMEDIUM

Tool Status

ToolStatusNotes
Shell Execution✅ CompleteWith security validation
File System✅ CompleteVirtual paths, sandboxing
Web Search✅ CompleteTavily + DuckDuckGo
Browser Control✅ CompletePlaywright-based
Git Operations⚠️ PartialBasic via shell
Email/Calendar❌ MissingPersonal assistant gap

Priority Definitions

HIGH Priority

  • Blocks core use cases
  • Users cannot accomplish primary goals without it
  • Examples: Missing critical tool, broken channel

MEDIUM Priority

  • Enhances capabilities
  • Users can work around it but experience is degraded
  • Examples: Missing convenience feature, partial implementation

LOW Priority

  • Nice to have
  • Improves polish but not essential
  • Examples: UI improvements, advanced features

Gap Documentation Template

When documenting a gap:

markdown
## Gap: {Feature Name}

**Status**: ❌ Missing / ⚠️ Partial
**Priority**: HIGH / MEDIUM / LOW
**Blocks**: {What use cases are blocked}

### Current State
{What exists today, if anything}

### Required State
{What the PRD/Architecture specifies}

### Gap Details
{Specific missing pieces}

### Effort Estimate
{Hours/days to implement}

### Dependencies
{What must be done first}

### Recommended Sprint
{Which sprint should address this}

Performing a Gap Review

  1. Read the latest documentation review:

    code
    read_file path="/docs/DOCUMENTATION_REVIEW_2026-01-28.md"
    
  2. Check the roadmap:

    code
    read_file path="/docs/ROADMAP.md"
    
  3. Review sprint breakdown:

    code
    read_file path="/docs/SPRINT_1_2_TASK_BREAKDOWN.md"
    
  4. Run tests to verify current state:

    bash
    cd apps/agent && uv run pytest --cov
    cd apps/gateway && npm test
    

Key Gaps to Track

Production Blockers

  • Test coverage < 80%
  • No deployment documentation
  • No API usage tracking

Feature Gaps

  • WhatsApp channel
  • Signal channel
  • Email integration
  • Calendar integration

Enhancement Gaps

  • Skill registry integration
  • Automatic model failover
  • Inter-session communication

Further Reading

  • Latest review: /docs/DOCUMENTATION_REVIEW_2026-01-28.md
  • Production plan: /docs/PRODUCTION_READINESS_PLAN.md
  • Roadmap: /docs/ROADMAP.md