What problem does it solve? Turning a described initiative into an executable, dependency-ordered task list is slow and error-prone when done by hand, especially when repo-specific rules in AGENTS.md, CLAUDE.md, and docs must be respected. This Skill automates the generation of a structured TASKS.md registry grounded in the actual repository context. ## Core Features & Use Cases - Initiative-Aware Task Generation: Loads the initiative folder under docs/described/<slug>/ (master plan, blueprint, decisions, QA notes) before writing any tasks. - Repo Rule Compliance: Treats AGENTS.md, CLAUDE.md, and repo docs as first-class rule sources and surfaces conflicts before generating dependent tasks. - Structured TASKS.md Output: Produces task IDs, statuses, owner lanes, dependencies, acceptance criteria, verification commands, manual QA expectations, and a progress log. - Use Case: After drafting a master plan for a new dashboard feature in docs/described/dashboard-publish/, run /describe-tasks dashboard-publish to get an executable, dependency-ordered TASKS.md that follows the repo's naming and verification conventions. ## Quick Start Ask the assistant to run /describe-tasks followed by your initiative slug to regenerate TASKS.md for that initiative.