← ClaudeAtlas

ensemble-create-trd-foremanlisted

Create Foreman-native structured Technical Requirements Document from PRD — omits adversarial review phase, outputs parser-compatible tables (Codex skill for /ensemble:create-trd-foreman)
FortiumPartners/ensemble · ★ 10 · Data & Documents · score 78
Install: claude install-skill FortiumPartners/ensemble
# Ensemble Command: /ensemble:create-trd-foreman This Codex skill mirrors the Ensemble slash command `/ensemble:create-trd-foreman`. Follow the workflow below, adapt to the current repository, and keep outputs structured. <!-- DO NOT EDIT - Generated from create-trd-foreman.yaml --> <!-- To modify this file, edit the YAML source and run: npm run generate --> Create a Foreman-native Technical Requirements Document (TRD) from a Product Requirements Document (PRD). The resulting TRD must be machine-consumable by Foreman's existing `parseTrd()` parser and suitable for immediate native task creation via `foreman sling prd`. Perform PRD validation, architecture design with alternatives, and a structured task breakdown with deterministic markdown tables. All outputs are saved to docs/TRD/. ## Workflow ### Phase 1: PRD Ingestion and Validation **1. PRD Ingestion** Parse and analyze existing PRD document from $ARGUMENTS path - Read PRD file from specified path - Validate document structure (required sections present) - Extract key requirements with REQ-NNN IDs - Build requirements registry for traceability tracking **2. Requirements Validation** Ensure completeness of functional and non-functional requirements - Validate all required sections present (Product Summary, User Analysis, Goals, Technical Requirements, Acceptance Criteria) - Check acceptance criteria are testable and use Given/When/Then format - Verify REQ-NNN format numbering is consist