smith-tasks

Convert plan.md and spec.md into a dependency-ordered tasks.md document.

50|8|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ATTCKDigital/smith --skill smith-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smith-tasks
Source: https://github.com/ATTCKDigital/smith/tree/main/skills/smith-tasks
Command: npx skills add https://github.com/ATTCKDigital/smith --skill smith-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Converts design artifacts into an actionable, dependency-ordered tasks document to drive consistent implementation and tracking.

## Core Features & Use Cases

  • Phase-driven task generation from plan.md and spec.md
  • Dependency graphs to plan parallel work
  • Traceability via strict checklist format and design artifact mapping
  • Use case: Given plan.md and spec.md, generate a ready-to-run tasks.md for development.

### Quick Start Run smith-tasks at the project root to generate tasks.md from the available design artifacts.

Frequently Asked Questions about smith-tasks

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

FAQPage Schema
How do I generate a tasks.md file from design artifacts?

To generate a tasks.md file from design artifacts, run the tool at your project root. It reads plan.md and spec.md to produce a dependency-ordered tasks document mapping user stories to actionable development phases.

What is dependency-ordered task generation from spec.md and plan.md?

Dependency-ordered task generation is the process of reading plan.md and spec.md to create a structured tasks.md. It maps user stories into sequential phases and highlights dependencies to plan parallel development work.

Can I generate a development checklist from user stories and a spec?

Yes, you can generate a development checklist from user stories and a spec. The tool reads your spec.md and plan.md files to output a strict checklist format tasks.md, ensuring full traceability between design artifacts and implementation steps.

What's the best way to convert a feature spec into actionable development tasks?

The best way to convert a feature spec into actionable development tasks is using an automated task-generation tool. It analyzes your plan.md and spec.md to build a complete tasks.md document, organizing stories into dependency-driven phases.

Do I need plan.md and spec.md to generate a dependency graph for tasks?

Yes, you need plan.md and spec.md files to generate a dependency graph for tasks. These design artifacts provide the required feature context and user stories needed to map out phases and dependencies for parallel work.