skills.rest
ab300819
ab300819COMMUNITY
Explore all skills by this author →
GitHub

dev-tasks

Decomposes system design documents into layered, traceable development tasks with dependencies and acceptance criteria.

Updated Jan 12, 2026
Search Tags:#tdd#task breakdown#acceptance criteria#sprint planning#traceability#dependency graph#documentation-driven
One-click install
npx skills add https://github.com/ab300819/keel-workflow --skill dev-tasks-ab300819
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-tasks
Source: https://github.com/ab300819/keel-workflow/tree/main/skills/dev-tasks
Command: npx skills add https://github.com/ab300819/keel-workflow --skill dev-tasks-ab300819

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a system design into an actionable development plan is error-prone: tasks end up too coarse, dependencies are unclear, and traceability back to requirements is lost. This Skill converts keel design and test-case documents into a structured task list where every task is testable, acceptable, and reviewable. ## Core Features & Use Cases - Layered Task Breakdown: Classifies tasks into four layers (core logic, API, UI, infrastructure) with risk-based review profiles (fast/guarded/audit) and TDD execution guidance per layer. - Requirement Traceability: Every task links back to feature IDs (F-XXX), acceptance criteria (AC-XXX), constraints (CON-XXX), and test cases (UT/IT/E2E-XXX), with a dependency graph and cycle-free ordering. - Incremental & Realign Modes: Appends or inserts tasks from feature/bugfix/insights flows, backfills design references for UI tasks, and upgrades existing task documents to newer spec versions without touching task status. - Use Case: After finishing system design and test cases for a new feature, run the Skill to produce 04-dev-tasks.md with 10+ TAR-compliant tasks, then hand them to the dev-workflow executor for TDD-based implementation. ## Quick Start Ask the assistant to split the completed system design into development tasks by running /dev-tasks, then confirm the generated task document before starting execution.

Frequently Asked Questions about dev-tasks

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

FAQPage Schema
How do I break a system design into development tasks?▼

Run /dev-tasks after completing the requirements, system design, and test-case documents. It reads all three, maps modules to tasks, assigns layers and review profiles, defines dependencies, and writes the result to docs/devdocs/04-dev-tasks.md for your confirmation.

What is the TAR principle in task planning?▼

TAR stands for Testable, Acceptable, and Reviewable. Every task must include a concrete test method, quantifiable acceptance criteria, and code review focus points, with specific file paths rather than vague references like related files.

Can I add tasks incrementally for a bugfix or new feature?▼

Yes. Tasks from feature, bugfix, or insights flows are appended or inserted into the existing task list with renumbered IDs and updated dependencies. High-priority bugfix tasks can be inserted ahead of pending work.

Does dev-tasks write implementation code?▼

No. It is strictly a documentation-phase Skill and is forbidden from producing source code or config changes. Task execution must go through /dev-workflow, which preserves the traceability matrix that /sync relies on.

When should I use dev-tasks realign mode?▼

Use /dev-tasks --realign (or /pipeline realign) when the task document spec version changes and existing documents need missing fields or structure backfilled. It only fixes documentation gaps and never adds, removes, or changes task status.

Related Skills

Explore More Software Engineering Skills→
ab300819ab300819

devdocs-dev-tasks

Break down system design documents into prioritized development tasks with dependencies.

Community
Basic
Ibrahim-3dIbrahim-3d
371

loop-executor

Automates sequential execution of verified plans with TDD integration and automatic commits.

Community
Advanced
alexandremendoncaalvaroalexandremendoncaalvaro
728

ad-audit

Audit AGENTS.md, ARCHITECTURE.md, and ADR statuses for documentation drift.

Community
Intermediate
haitao2016haitao2016

super-game-dev

Manage the game development lifecycle with an 8-stage gated pipeline.

Community
Advanced