← ClaudeAtlas

ensemble-analyze-requirementslisted

Pre-implementation cross-artifact consistency sweep — checks PRD↔TRD↔beads alignment before coding begins (Codex skill for /ensemble:analyze-requirements)
FortiumPartners/ensemble · ★ 10 · Web & Frontend · score 78
Install: claude install-skill FortiumPartners/ensemble
# Ensemble Command: /ensemble:analyze-requirements This Codex skill mirrors the Ensemble slash command `/ensemble:analyze-requirements`. Follow the workflow below, adapt to the current repository, and keep outputs structured. <!-- DO NOT EDIT - Generated from analyze-requirements.yaml --> <!-- To modify this file, edit the YAML source and run: npm run generate --> Perform a holistic pre-implementation sweep across PRD, TRD, and (if available) the task bead list. Check that the PRD is structurally complete, that every REQ-NNN has TRD coverage, that no cross-document contradictions exist, that all [satisfies] annotations reference real PRD IDs, that every implementation task has a paired -TEST task, and that all AC references in TRD are valid. Produce a READINESS SCORE and actionable remediation suggestions. ## Workflow ### Phase 1: Input Validation **1. Argument Resolution** Verify that both required arguments are provided and that both files exist on disk. If $ARGUMENTS does not contain two tokens: print 'ERROR: Usage: /ensemble:analyze-requirements <prd-path> <trd-path>' and EXIT with code 1. Resolve PRD_PATH from the first argument. If file does not exist: print 'ERROR: PRD file not found: <PRD_PATH>' and EXIT with code 1. Resolve TRD_PATH from the second argument. If file does not exist: print 'ERROR: TRD file not found: <TRD_PATH>' and EXIT with code 1. **2. Document Loading** Read both documents into memory for analysis. Read PRD_PATH in full. Record the