prd-taskmasterlisted

# PRD Generator v3.0 — GitHub Issue + Shape-Spec Pipeline Generate comprehensive, zero-compromise PRDs, publish them as GitHub issues, and trigger `/agent-os:shape-spec` with a scope-aware orchestration prompt that enforces Opus 4.6, one-shot delivery, and `/pr-handoff-to-codex` as final validation. Source attribution: this bundled skill is sourced from `anombyte93/prd-taskmaster` and references Task Master / `task-master-ai` for downstream task orchestration. ## When to Use This Skill Activate when user: - Requests a PRD or product requirements document - Says "I want a PRD", "create requirements", "write requirements" - Asks to plan a feature for implementation - Wants to document product/feature requirements for engineering Do NOT activate for: - Code documentation (API docs, technical reference) - Test specifications or QA documentation - Project management timelines without product context - PDF document creation ## Core Principles **Nothing Is Deferred. Ever.** Phases are fine for sequencing work. But there are NO "nice-to-haves," "future work," "stretch goals," or "do laters." Every requirement in the PRD is a must-deliver. If something isn't important enough to build, it doesn't belong in the PRD at all. **GitHub Issue Is the Source of Truth** The full PRD is published as a GitHub issue. This is what agents, shape-spec, and pr-handoff-to-codex reference. **Shape-Spec Orchestrates Execution** After the PRD is published, `/agent-os:shape-spec` is triggered with