openspec-plus-tasks

Generates OpenSpec tasks.md files organized as dependency-ordered vertical slices with subagent compliance review.

1|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/WndDnz/modelo-relatorio-unifei-ict --skill openspec-plus-tasks-wnddnz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-plus-tasks
Source: https://github.com/WndDnz/modelo-relatorio-unifei-ict/tree/main/.opencode/skills/openspec-plus-tasks
Command: npx skills add https://github.com/WndDnz/modelo-relatorio-unifei-ict --skill openspec-plus-tasks-wnddnz

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about openspec-plus-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an OpenSpec tasks.md file?

Run the tasks phase after completing the proposal, specs, and design. The skill resolves the template with `openspec instructions tasks --json`, discovers vertical slices through clarifying questions, writes tasks.md, and runs a subagent review before surfacing it for approval.

What is a vertical slice in task planning?

A vertical slice is a task group that spans all needed layers (DB, API, UI, CLI) and produces one end-to-end testable outcome when complete. It replaces layer-based grouping so every finished group lets the user verify something works.

Can tasks.md include code snippets or file lists?

No. Tasks state what behavior to deliver, not how. Code snippets, shell commands, commit messages, and custom sections like Files or Dependencies are prohibited; the design document holds implementation detail.

Does the skill read source code during task generation?

No. Reading source code is explicitly forbidden. The design phase is expected to have grounded all patterns; if detail is missing, the gap is surfaced to the user instead of being resolved by inspecting code.

What happens if the reviewer subagent finds issues?

Issues are fixed inline in the root context and the corrected tasks.md is surfaced for user review. The reviewer is dispatched exactly once and is never re-dispatched after fixes.