hf-tasks

Convert approved designs into traceable task plans with dependencies and milestones.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hujianbest/garage-agent --skill hf-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf-tasks
Source: https://github.com/hujianbest/garage-agent/tree/main/packs/coding/skills/hf-tasks
Command: npx skills add https://github.com/hujianbest/garage-agent --skill hf-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a structured bridge from approved specifications or designs to actionable, traceable task units that can be reviewed and executed, reducing ambiguity and rework.

Core Features & Use Cases

  • Converts approved specs/designs into granular, verifiable tasks with defined acceptance criteria and dependencies.
  • Produces artifacts such as a tasks.md plan and an accompanying lightweight task board to support hf-tasks-review.
  • Provides end-to-end traceability from requirements/designs to concrete work items for audits and collaboration.

Quick Start

Start by supplying an approved spec or design, then generate a draft tasks.md that decomposes it into small, verifiable tasks.

Frequently Asked Questions about hf-tasks

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

FAQPage Schema
How do I turn approved design specs into an executable task plan?

To turn approved design specs into an executable task plan, supply the stable specification to generate a draft tasks.md that decomposes it into small, verifiable tasks with defined acceptance criteria and dependencies.

What is requirements traceability in project task planning?

Requirements traceability in task planning maps concrete work items back to original design specifications, providing end-to-end visibility for audits and collaboration while reducing ambiguity and rework.

How do I create a task board with dependency mapping and milestones?

You can create a task board with dependency mapping by converting approved specs into a structured tasks.md plan, which automatically wires milestones, defines ready/blocked states, and outputs an accompanying lightweight task board.

How do I define the Definition of Done for task breakdown in agile workflows?

Defining the Definition of Done for task breakdown involves enforcing specific DoD criteria during the conversion of approved designs, ensuring each generated task unit is granular and verifiable before execution.

Does this task planning approach work for specs that are still changing?

No, this task planning approach applies specifically across workflows where specs are stable but implementation planning is pending, ensuring the generated task plans and dependency graphs remain executable and verifiable.

What is the best way to map dependencies for verifiable task units?

The best way to map dependencies for verifiable task units is to process an approved design through a structured breakdown that generates a dependency graph, enforcing ready and blocked states to guide execution order.