What problem does it solve? Writing an OpenSpec tasks.md often produces layer-based task groups (DB, API, UI) that are not independently testable, or tasks that leak implementation detail. This Skill enforces vertical-slice discipline and a mandatory review pass so every task group delivers one testable outcome. ## Core Features & Use Cases - Vertical-Slice Discovery: A mandatory discovery phase identifies slices, names each slice's one-sentence testable outcome, and orders them by dependency before anything is written. - Template Compliance: Resolves the schema via openspec instructions tasks --json and writes tasks.md strictly following the project template, with no custom sections or code snippets. - Subagent Compliance Review: Dispatches a single-shot reviewer subagent that checks slice discipline, task granularity, spec/design coverage, and naming consistency, then applies findings inline. - Use Case: After finishing an OpenSpec proposal, specs, and design for a new feature, run the tasks phase to produce a tasks.md where each group is an end-to-end testable capability rather than a horizontal layer. ## Quick Start Ask the AI to generate the OpenSpec tasks.md for the current change using vertical slices and the reviewer check.