tasks

Generate dependency-ordered tasks.md with acceptance criteria and cross-verify designs in specs/{feature}.

7|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/skullninja/coco-workflow --skill tasks-skullninja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/skullninja/coco-workflow/tree/main/skills/tasks
Command: npx skills add https://github.com/skullninja/coco-workflow --skill tasks-skullninja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a dependency-ordered tasks.md and perform cross-artifact consistency analysis from design.md in specs/{feature}/.

Core Features & Use Cases

  • Generate a tasks.md organized by user story with explicit acceptance criteria and dependency mapping.
  • Run cross-artifact consistency analysis against design documents in specs/{feature}/.
  • Output a deterministic plan ready for import into trackers, with legacy artifact support.

Quick Start

Use the tasks skill to generate specs/{feature}/tasks.md from the current design artifacts in specs/{feature}.

Frequently Asked Questions about tasks

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

FAQPage Schema
How do I generate dependency-ordered tasks from design specs?

To generate dependency-ordered tasks, the skill reads design documents from specs/{feature}/ and outputs a deterministic tasks.md organized by user story with explicit acceptance criteria and dependency mapping.

What is cross-artifact consistency analysis for user stories?

Cross-artifact consistency analysis checks generated user stories and tasks against existing design documents to ensure alignment and integration-ready outputs within your planning workflow.

Can I use this to generate a tasks.md file for an existing feature?

Yes, you can generate a tasks.md file for an existing feature by running the skill against the current design artifacts stored in the specs/{feature}/ directory.

Does the generated task plan include acceptance criteria and dependency mapping?

Yes, the generated task plan includes explicit acceptance criteria and dependency mapping, producing a deterministic plan ready for import into trackers with legacy artifact support.

What format do my design documents need to be in for task generation?

Design documents must be stored as design.md within the specs/{feature}/ directory structure to successfully generate the dependency-ordered tasks.md and perform consistency analysis.

Why are my generated tasks not matching the design specs?

If generated tasks do not match design specs, run the cross-artifact consistency analysis to identify misalignments between your user stories and the source design documents in specs/{feature}/.