task-breakdown

Name: task-breakdown
Availability: InStock
Author: junior-frontend-dev

Convert architecture plans into atomic tasks with verification criteria and file operations.

Updated Jan 10, 2026

Search Tags:#planning #architecture #templates #verification #project-management #file-operations #task-breakdown

Ready to run

npx skills add https://github.com/Junior-Frontend-dev/Hi-u-ng --skill task-breakdown-junior-frontend-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-breakdown
Source: https://github.com/Junior-Frontend-dev/Hi-u-ng/tree/main/.claude/skills/planning/task-breakdown
Command: npx skills add https://github.com/Junior-Frontend-dev/Hi-u-ng --skill task-breakdown-junior-frontend-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Breaks down high-level architecture plans into atomic, execution-ready tasks with explicit file paths, line numbers, and verification steps.

Core Features & Use Cases

Atomic Tasks: each task targets a single change with clear acceptance criteria.
Execution Readiness: tasks include file operation guidance (CREATE, MODIFY, etc.) and dependency tracking.
Reusable Templates: uses the provided task-template.md to standardize outputs.

Quick Start

Provide an architecture plan and run the task breakdown to produce a ready-to-implement task list.

Frequently Asked Questions about task-breakdown

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

FAQPage Schema

How do I break down an architecture plan into executable coding tasks?▼

Task breakdown standardizes project management by converting architecture plans into atomic tasks with explicit file operations, dependency tracking, and verification criteria to ensure deterministic delivery.

What is the best way to ensure my development tasks include specific file operations and dependencies?▼

During design-to-code transitions, task breakdown enforces a standardized template that maps high-level architecture changes to atomic file operations and explicit dependencies.

How do I generate a task list with verification criteria from a software design document?▼

Apply task breakdown to high-level architecture plans to produce execution-ready tasks with clear acceptance criteria, explicit dependencies, and commit-oriented outputs for software projects.

Does task breakdown work for converting high-level project plans into atomic single-change tasks?▼

Task breakdown handles architecture-to-implementation handoffs by generating atomic tasks with explicit file paths, line numbers, and verification steps, ensuring deterministic delivery without external dependencies.

Can I standardize my work breakdown structure using a reusable template for software projects?▼

Task breakdown standardizes work breakdowns by applying a reusable template to produce atomic tasks with explicit file paths, dependency tracking, and verification steps for deterministic delivery.