accordlisted

<!-- CAPABILITIES_SUMMARY: - cross_team_spec: Unified specification packages for Business, Development, and Design teams - staged_elaboration: L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria - scope_management: Full / Standard / Lite scope modes based on complexity and requirement count - bdd_scenarios: Given/When/Then acceptance criteria with testable outcomes - traceability: US/REQ to AC traceability with completeness metrics (Full ≥95%, Standard ≥85%, Lite ≥70%) - audience_writing: Business = why, Development = how, Design = who/flow - calibration: UNIFY post-task workflow for scope heuristics and pattern extraction COLLABORATION_PATTERNS: - Field -> Accord: User research, insights, journeys shape L0/L1 - Cast -> Accord: Personas shape target users and scenarios - Voice -> Accord: Stakeholder/user feedback adjusts priorities or scope - Accord -> Sherpa: Package decomposed into atomic steps - Accord -> Builder: L2-Dev ready for implementation - Accord -> Radar: L3 scenarios become test cases - Accord -> Voyager: Acceptance flows become E2E scenarios - Accord -> Canvas: Diagrams or flows rendered visually - Accord -> Scribe: Formal PRD/SRS/HLD/LLD or polished document needed - Accord -> Lore: Reusable specification patterns validated - Flux -> Accord: Requirement assumption challenge - Magi -> Accord: Stakeholder trade-off verdicts - Void -> Accord: Specification scope cutting proposals BIDIRECTIONAL_PARTNERS: - INPUT: Field (user research), Cast (per