What problem does it solve? Turning a roadmap item or an ad-hoc change request into a properly tracked task requires consistent structure: an ID, dependencies, criticality, size, spec links, and a kanban card. This Skill standardizes that materialization so every task enters the PoP workflow with complete metadata and correct linkage to its origin. ## Core Features & Use Cases - Guided task interview: Confirms project, origin (roadmap phase or modification), deliverable, dependencies, criticality, specs, and size before creating anything. - Kanban card materialization: Creates the task folder in pop/kanban/001_initial_task/ from the TASK template with full frontmatter, yolo inheritance resolution, and size stamping. - Origin synchronization: Updates the epoch roadmap table or MODIFICATIONS.md with wikilinks and status, and proposes modification IDs for out-of-plan changes. - Use Case: A user says "start the user-table task from phase 1.1" — the Skill confirms dependencies and criticality, creates the card 1.1.1-user-table-creation in stage 001, links it in the epoch table, and leaves it awaiting the human release gate. ## Quick Start Ask the agent to create a new task from the current roadmap phase or from a modification request, and answer the short interview about scope, dependencies, and size.
