Skip to content

SDK feature parity: 29 features need active exercise testing #340

@bradygaster

Description

@bradygaster

Summary

Systematic SDK-first feature parity testing in the SdkSquad test bed has identified 29 features that need active exercise testing. These features have correct filesystem setup (configs, templates, routing rules exist) but their runtime behavior hasn't been verified for SDK squads.

This issue tracks the remaining test matrix. Each feature category below needs a dedicated test session.

Test Matrix — Remaining Features

P1: Workflow Features (7 features)

# Feature What to Test
19 Directive capture Give "Always..." directive → verify inbox capture
20 Eager execution Multi-domain task → verify anticipatory spawns
22 GitHub repo connection Connect to repo → verify Issue Source in team.md
23 Issue triage Label issue squad → verify Lead assigns squad:{member}
24 Issue lifecycle Issue → branch → PR → merge flow
25 Label routing Apply squad:{name} → verify agent dispatch
29-32 Ralph (4 features) Activation, work-check, idle-watch, watch mode

P2: Advanced Features (12 features)

# Feature What to Test
26-28 Ceremonies (3) Auto-trigger, manual, cooldown
33-35 PRD Mode (3) Intake, decomposition, work routing
36-38 Human & Copilot (3) Add human, add @copilot, auto-assign
39-40 Skills (2) Agent extraction, confidence lifecycle

P3: Platform & Edge Cases (9 features)

# Feature What to Test
42 Worktree awareness Multi-worktree team root resolution
45-46 Reviewer protocol (2) Rejection lockout, deadlock escalation
47 Client compatibility VS Code mode detection & degradation
48 MCP integration Tool discovery, graceful degradation
49 Constraint budget Counter display during constrained tasks
50 Multi-agent artifact Assembled result + raw appendix format

Already Verified (this session)

# Feature Status
17 Skill-aware routing ✅ Verified — skills/ exists with correct format
44 Merge drivers ✅ Verified — .gitattributes has merge=union rules
33 PRD intake ✅ Partially verified — PRD.md exists, referenced in decisions

Blocking Issues

Test Bed

  • Repo: SdkSquad (Snake game, vanilla JS)
  • PRD: PRD.md at repo root tracks all 50 features
  • Squad: Matrix universe (Neo, Tank, Switch, Dozer, Scribe, Ralph)

Exit Criteria

Every feature is either:

  • ✅ Verified — tested and confirmed working in SDK squad
  • 🚫 Scoped out — explicitly excluded with rationale

No ⚠️ Untested or ❌ Known Gap items remain.

Metadata

Metadata

Assignees

No one assigned

    Labels

    go:needs-researchNeeds investigationsquadSquad triage inbox — Lead will assign to a membersquad:fidoAssigned to FIDO (Quality Owner)type:bugSomething broken

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions