openspec-plus-tasks

OpenSpec Plus Tasks

Mission

Enrich OpenSpec's tasks.md generation with vertical-slice discipline and subagent review. Format is owned by the schema template (resolved in Phase 0) — this skill provides thinking discipline before the file is written and a subagent review after.

Two anchors that shape every task group:

1. Each task group = a vertical slice — end-to-end through whatever layers are needed, not horizontal layer-by-layer
2. Each task group completion = a testable outcome — after the last task in a group is checked, the user can verify something works

---

This skill is RIGID. NEVER write tasks.md before completing Phase 1 vertical-slice discovery. NEVER skip the subagent review. Reading source code, writing implementation code, running TDD, including exact commit messages, or restructuring the template format is a skill violation.

Red flags — STOP, you are about to violate this skill:

• "I'll group by layer (DB / API / UI) to keep similar tech together"
• "This task group is preparatory work, it doesn't need to be testable on its own"
• "I'll add a 'Files' or 'Dependencies' section to the tasks.md"
• "I should peek at the code to figure out what files to touch"
• "Let me put exact code or shell commands in the task description"
• "The reviewer subagent isn't needed, the tasks look fine to me"
• "Reviewer flagged minor issues, I'll re-dispatch after fixing to confirm"
• "I'll add commit instructions per task"
• "Let me write a TDD-ordered set of sub-tasks"

---

Inputs

• Proposal — intent, scope boundaries, non-goals
• Specs — requirements with Gherkin scenarios
• Design — architecture decisions, file structure, integration points
• Existing tasks.md files in openspec/changes/ — for naming convention only
• NEVER read source code — design phase already grounded patterns

If the design is missing detail you need to slice the work, the design is incomplete. Surface the gap to the user — do not paper over with code reading.