dev.tasks

Convert feature design artifacts into a dependency-ordered tasks.md file.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Obsidian-Owl/agentlint --skill dev-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev.tasks
Source: https://github.com/Obsidian-Owl/agentlint/tree/main/.claude/skills/dev.tasks
Command: npx skills add https://github.com/Obsidian-Owl/agentlint --skill dev-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

This Skill converts feature design artifacts into a structured, executable tasks.md, ensuring a clear handoff from design to implementation.

Core Features & Use Cases

  • Dependency-ordered Task Generation: Produces a prioritized, execution-ready list of tasks from artifacts like spec.md and plan.md.
  • Story-driven Breakdown: Converts prioritized user stories into actionable tasks with clear acceptance criteria and tracing to FR/NFR.
  • Collaboration-ready Output: Generates a ready-to-import tasks.md suitable for project management tools and team alignment.

Quick Start

Use the dev.tasks skill on a feature branch with spec.md and plan.md present to generate tasks.md.

Frequently Asked Questions about dev.tasks

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

FAQPage Schema
How do I generate a task breakdown from feature design artifacts?

To generate a task breakdown, the skill converts feature design artifacts like spec.md and plan.md into a structured tasks.md. It extracts user stories, priorities, and technical context to produce a ready-to-use execution plan.

What is the best way to structure tasks with execution order and dependencies?

The best way to structure tasks with execution order and dependencies is by formatting them in the T### format with absolute file paths. This ensures a clear handoff from design to implementation and provides traceability to FR/NFR.

Do I need spec.md and plan.md to generate a tasks.md file?

Yes, you need spec.md and plan.md present on your feature branch to generate a tasks.md file. These feature design artifacts provide the user stories and technical context required for the task breakdown.

Can I trace user stories to acceptance criteria in the generated task plan?

Yes, you can trace user stories to acceptance criteria in the generated task plan. The skill creates a story-driven breakdown that formats actionable tasks with clear acceptance criteria and tracing to FR/NFR.

How does the T### task format work for project management tools?

The T### task format works by producing a collaboration-ready tasks.md that is suitable for importing into project management tools. It formats prioritized user stories into an execution-ready list for team alignment.

Does the task generation skill work without jq installed?

No, the task generation skill requires jq to be installed. This dependency is necessary for the script component to process feature design artifacts and extract the required user stories and technical context.