tasks

Generate dependency-ordered tasks.md from design documents for feature implementation.

52|3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill tasks-zte-aicloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/ZTE-AICloud/Co-OmniSpec/tree/main/skills/tasks
Command: npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill tasks-zte-aicloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Based on available design documents, this skill generates executable, dependency-ordered tasks (tasks.md) to streamline feature implementation.

Core Features & Use Cases

  • Generate a tasks.md from design.md, spec.md, and related docs to outline concrete tasks and milestones.
  • Map dependencies and identify parallelizable tasks to optimize planning.
  • Support multi-scenario features by linking design/spec content to individual task sets.

Quick Start

Generate a tasks.md from the available design documents to start planning feature implementation.

Frequently Asked Questions about tasks

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

FAQPage Schema
How do I generate an implementation plan from a design document?

To generate an implementation plan from a design document, this skill reads your design.md and spec.md files to produce a dependency-ordered tasks.md file. It maps dependencies and identifies parallelizable tasks to streamline feature implementation.

What is the best way to turn a feature spec into a dependency-ordered task list?

The best way to turn a feature spec into a dependency-ordered task list is using a task generation skill that maps spec content to scenarios. It outputs a ready-to-run tasks.md with defined file paths, clear sequencing, and dependency checkpoints.

Can I map dependencies and parallelize tasks from multiple design docs?

Yes, you can map dependencies and identify parallelizable tasks from multiple design docs. This skill links multi-scenario design and spec content to individual task sets, optimizing planning by mapping dependencies across the generated tasks.md.

Do I need a spec.md file to generate a tasks.md for feature development?

Yes, you need available design documents like spec.md and design.md to generate a tasks.md for feature development. The skill loads design and spec data to map scenarios and produce a ready-to-run task list with defined file paths and checkpoints.

When should I not use automated task generation from design documents?

You should not use automated task generation from design documents if your feature lacks a defined spec or design doc. The skill requires available design documents to load data, map scenarios, and produce a dependency-ordered tasks.md with clear sequencing.