What problem does it solve? Turning a product requirements document into trackable, well-scoped work items is manual and error-prone: tasks end up duplicated, poorly sliced, or missing acceptance criteria. This Skill converts a PRD into atomic, phased task files that follow the repository's task-management convention. ## Core Features & Use Cases - PRD ingestion from multiple sources: Accepts a GitHub issue number (fetched via gh issue view), a file path, or PRD content already in the conversation. - Vertical slicing and phasing: Breaks the PRD into atomic, independently completable vertical slices, each split into committable phases with acceptance criteria. - Duplicate detection: Runs a discovery scan across inbox, active and archived tasks, roadmaps, docs, and code before creating anything, so existing work is never silently duplicated. - Convention-compliant task creation: Creates area-prefixed task files with type, priority, spec refs, dependencies, and optional autonomy/repo metadata, then syncs ledgers via at ledger check and at repos-check. - Use Case: You have a PRD for a new authentication feature as GitHub issue #42. The Skill fetches it, proposes five phased tasks mapped to existing areas, checks for overlap with current work, and creates the task files after your approval. ## Quick Start Convert the PRD in docs/specs/auth-redesign.md into trackable tasks in docs/tasks_manager/_todos/ using the prd-to-todos workflow.
