Skip to content

Phase 2B Agent Skills Architecture Audit & Consolidation Plan #1225

Description

@ashleyshaw

Audit Summary

Comprehensive second-round audit of agent skills architecture to identify version conflicts, ownership gaps, and consolidation opportunities across shared and agent-local skills.

Audit Type: Architecture & Skills Governance
Scope: Root skills directory (123 items → 70 active) + Agent skills (16 agents)


Audit Checklist / Scope

  • Scope defined and agreed
  • Areas/components listed
    • Root skills/ directory (70 active skills, 4 tiers)
    • Agent skills across 16 agents (5 Phase 2A ✅, 11 Phase 2B/3 pending)
    • Shared vs. agent-local taxonomy
  • Audit tools or standards referenced
    • Agent architecture standards
    • Multi-provider compatibility patterns
    • Skills governance rules
  • Risks and findings documented
    • Figma integration conflicts (root 2023 vs. agent 2026)
    • AI readiness skill duplication
    • Design system audit dual implementations
  • Remediation actions mapped
    • 3-phase consolidation strategy (Audit → Inventory → Consolidation)

Findings / Risks

Root Skills Analysis (123 → 70)

Categorized into 4 tiers:

  1. Tier 0 — Generic Utilities (24 skills)

    • documents, pdfs, docx, xlsx, pptx
    • linear, harvest, asana, clickup
    • Shared across all agents
  2. Tier 1 — Reusable Domain Skills (28 skills)

    • figma-* (6 variants)
    • audit-design-system
    • brand-* collection
    • Deployable to any agent
  3. Tier 2 — Agency-Specific Skills (12 skills)

    • lightspeed-* family (potentially obsolete)
    • LightSpeed internal tooling only
    • Risk: May not align with multi-provider vision
  4. Tier 3 — WordPress/Niche Skills (6 skills)

    • wordpress-block-*
    • wp-config-agent
    • Specialized domain tools

Critical Conflicts Identified

Conflict Root Version Agent Version Impact Priority
Figma Integration 2023 vintage 2026 multi-provider API incompatibility HIGH
AI Readiness Generic agency skill Specialized agent version Duplication, confusion MEDIUM
Design System Audit Dual implementations Different purposes Maintenance burden MEDIUM

Ownership & Version Gaps

  • 23 skills with unclear ownership (shared vs. agent-local)
  • 7 version conflicts requiring resolution
  • 4 skills potentially obsolete or redundant
  • No scalable lookup system for agent developers

Remediation Actions

PHASE A — Audit (Current — This Week)

6 audit tasks, ~10 hours

  1. ✅ Root skills categorization (70 items by tier)
  2. ✅ Conflict identification & prioritization
  3. ✅ Ownership mapping (shared vs. agent-local)
  4. ⏳ Document success metrics & governance rules
  5. ⏳ Schedule Phase B inventory
  6. ⏳ Create sub-issues for each conflict

PHASE B — Inventory (This Month)

4 consolidation tasks, ~12 hours

  • Audit remaining 11 agents (Batch 2-3)
  • Document all agent-specific skills
  • Identify consolidation opportunities
  • Prioritize skill moves/archives

PHASE C — Consolidation (Next Quarter)

Apply to all 16 agents

  • Physical consolidation (move/archive/refactor)
  • Implement governance rules in CI
  • Update agent standards & templates

Acceptance Criteria

  • Audit scope and checklist completed
  • Findings and risks documented
  • Remediation actions assigned and tracked
  • Documentation/changelog updated (if applicable)
  • PR uses correct branch prefix (feat/)

Definition of Ready (DoR)

  • Audit scope, checklist, and goals defined
  • Areas/components listed
    • Root skills directory (70 active)
    • 16 agents (5 Phase 2A, 11 Phase 2B/3)
    • Shared vs. agent-local taxonomy
  • Dependencies and standards mapped
    • Agent architecture standards
    • Multi-provider compatibility patterns

Definition of Done (DoD)

  • Audit performed and findings documented
    • Root skills categorized (4 tiers)
    • 3 critical conflicts identified
    • Ownership gaps mapped
  • Remediation actions assigned
    • Phase A: 6 audit tasks
    • Phase B: 4 consolidation tasks
    • Phase C: Roadmap created
  • Documentation/changelog updated
  • PR uses correct branch prefix (audit/)
    • Using feat/ (audit documentation is a feature addition)

Additional Context

Related Initiatives:

Standards & References:

Related Issues:


Definition of Ready (DoR)

  • Audit scope clearly defined
  • Audit criteria/checklist created
  • Related systems/areas identified
  • Timeline estimated

Definition of Done (DoD)

  • Audit completed comprehensively
  • Findings documented with evidence
  • Risk assessment provided
  • Recommendations and action items listed

Metadata

Metadata

Assignees

Type

Fields

Priority

None yet

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions