ensemble-requirement-statuslisted

# Ensemble Command: /ensemble:requirement-status This Codex skill mirrors the Ensemble slash command `/ensemble:requirement-status`. Follow the workflow below, adapt to the current repository, and keep outputs structured. <!-- DO NOT EDIT - Generated from requirement-status.yaml --> <!-- To modify this file, edit the YAML source and run: npm run generate --> Scan the root epic bead and all child task beads for req-verified: tokens written by implement-trd-beads when test tasks close. Cross-reference against the PRD REQ-NNN list to produce a requirement satisfaction table showing which requirements are verified, which are in-progress, and which are not yet started. ## Workflow ### Phase 1: Context Resolution **1. TRD Slug Resolution** Resolve the TRD slug from $ARGUMENTS. If $ARGUMENTS is a file path: derive TRD_SLUG from filename (lowercase, replace non-alphanumeric with hyphens). If $ARGUMENTS is a slug string: use directly as TRD_SLUG. If $ARGUMENTS empty: list recent TRD-prefixed epics via br list --status=open --json and prompt user. If br list returns no TRD-prefixed epics: print 'No TRD implementations found in beads storage. Run /ensemble:implement-trd-beads first.' and EXIT. **2. Root Epic Location** Find the root epic bead for this TRD. Run: br list --status=open --json Verify the output is valid JSON (starts with '['). If not: print 'ERROR: br command failed or returned non-JSON output. Is br installed and configured? Output: <first 200 chars>' and EX