create-tasks

Generate dependency-ordered task lists from design documents into tasks.md files.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/japurcell/skills --skill create-tasks-japurcell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-tasks
Source: https://github.com/japurcell/skills/tree/main/skills/create-tasks
Command: npx skills add https://github.com/japurcell/skills --skill create-tasks-japurcell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a concrete, dependency-ordered tasks.md from design artifacts (plan.md, spec.md, data-model.md, contracts/) to enable independent story implementation and testing.

Core Features & Use Cases

  • Automates task creation by organizing work by user stories and phases (Setup, Foundational, US1/US2, Polish).
  • Produces a deterministic, checklist-style tasks.md with explicit file paths and dependencies.
  • Validates formatting, placeholders, and phase coverage to ensure production-ready outputs.

Quick Start

Run the task generation by supplying a plan.md; the tool will scan companion docs in .agents/scratchpad/<feature>/ and emit tasks.md with a verified structure.

Frequently Asked Questions about create-tasks

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

FAQPage Schema
How do I generate a tasks.md file from a plan.md and spec.md?

To generate a tasks.md file, supply a plan.md and the tool will scan companion design artifacts like spec.md, data-model.md, and contracts/ to produce a structured, dependency-ordered task checklist.

What is the best way to create dependency-ordered task lists from design documents?

Creating dependency-ordered task lists from design documents involves organizing work into phases like Setup, Foundational, and Polish, ensuring tasks follow an explicit dependency order for independent story implementation.

How do you structure task lists by user stories and implementation phases?

Structuring task lists by user stories and implementation phases requires grouping checklist items into Setup, Foundational, US1/US2, and Polish phases to enable independent story testing and execution.

Do I need a data-model.md and contracts directory to generate task plans?

You do not strictly need a data-model.md and contracts directory to generate task plans, but supplying a plan.md is required while companion artifacts in .agents/scratchpad/ enhance output validation and coverage.

How does placeholder validation work for executable task plans?

Placeholder validation for executable task plans works by enforcing a strict checklist format, verifying explicit file paths, and checking formatting and phase coverage to ensure production-ready task outputs.