Task breakdown from plan

Skill roronoazoroshao369/vibe-coding-os/skills/core/task-breakdown-from-plan

Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

Install

npx -y skills add roronoazoroshao369/vibe-coding-os --skill task-breakdown-from-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, as published. Nobody here has run it

Task Breakdown From Plan

Purpose

Decompose an implementation plan into small, reviewable, independently grabbable tasks with explicit dependencies, parallel markers, and test-first ordering.

When to use

Use after a plan is agreed and before implementation, especially when work can be parallelized, handed to multiple agents, or needs a clear order of execution.

Inputs

The agreed plan (steps, technical context, risks), acceptance criteria, and any constraints on ordering (shared interfaces, data migrations).

Workflow

Convert each plan step into one or more concrete tasks.
For each task, write a clear subject, the files involved, and a done condition.
Add a depends-on field listing prerequisite task IDs.
Mark tasks that can run concurrently with a parallel marker.
Sequence test tasks before the implementation tasks they cover (TDD ordering).
Confirm every acceptance criterion is covered by at least one task.
Record the ordering rationale so reviewers understand the dependency graph.

Outputs

A task list using templates/tasks-template.md with dependencies, parallel markers, TDD ordering, and acceptance-criteria coverage.

Failure modes

Tasks are too large or vaguely scoped to grab independently.
Hidden dependencies cause rework when tasks run out of order.
Implementation tasks precede their tests.
Some acceptance criteria have no covering task.

Verification checklist

Each task has a clear done condition and named files.
Dependencies are explicit; the graph has no cycles.
Parallelizable tasks are marked.
Test tasks precede their implementation tasks.
Every acceptance criterion maps to a task.

Applied / Not Applied

Applied: dependency-aware decomposition, parallel markers, and TDD ordering from github/spec-kit.
Not applied: upstream tasks template text or [P] syntax verbatim, and upstream command names. Complements (does not replace) skills/core/issue-slicing/SKILL.md, which slices ideas into issues; this skill turns an agreed plan into ordered tasks.

Ghi chú tiếng Việt

Chia kế hoạch thành các task nhỏ, độc lập, có depends-on, đánh dấu task song song, và xếp test trước implementation (TDD). Đảm bảo mọi tiêu chí chấp nhận đều có task. Khác với issue-slicing (chia ý tưởng thành issue); skill này biến plan thành task có thứ tự. Liên kết: skills/core/dependency-aware-task-ordering/SKILL.md, skills/core/test-driven-development/SKILL.md.