tasks

name	tasks
description	Break down a PRD into actionable tasks with dependencies, written to tasks.yaml. Use when the user wants to convert a PRD or feature description into trackable tasks.
argument-hint	<prd-path-or-description> [--name <feature-name>]

Break down a PRD into actionable tasks with dependencies following the task YAML spec.

Usage

/tasks [--name ]

Parameters

• prd-path-or-description: Either a file path to a PRD markdown file, or a description string (required)
• --name: Optional feature name (auto-generated from first 4 words if not provided)

Examples

/tasks prd/authentication/prd.md /tasks "Build user authentication with OAuth2 and JWT" /tasks ./features/search.md --name search-feature /tasks "Add real-time notifications with websockets" --name realtime-notif

Implementation

1. Parse input:

   • If input is a file path that exists: read contents as PRD
   • Otherwise: use input string as feature description

2. Generate feature name if not provided:

   • Use first 4 words, lowercase, hyphenated
   • Example: "Build user authentication system" → "build-user-auth-system"

3. Invoke the prd-planner subagent with:

   • feature_name:
   • description:
   • context:

4. The prd-planner executes 3 phases:

   • Phase 1: Research - Research best practices and patterns
   • Phase 2: Refine - Create/update PRD document
   • Phase 3: Create Tasks - Generate tasks.yaml with dependencies

Task YAML Spec

tasks:
  - key: task-name          # Unique kebab-case identifier
    description: Brief description of the task
    details: ./task-name.md # Path to detail file with implementation notes
    status: open            # open, progress, or done
    depends: []             # List of task keys this depends on

Output

✓ Tasks created: prd/{feature-name}/
  - prd.md
  - tasks.yaml (X tasks)
  - {X} detail files

Tasks:
  1. task-name-1 (no deps)
  2. task-name-2 (depends: task-name-1)
  ...

Manage tasks.yaml with uv run ~/.claude/skills/tasks/tasks.py (view status, CRUD on tasks) or run /code <tasks.yaml> to execute ready tasks.

Path resolution gotcha

tasks.py resolves the YAML path relative to the current working directory. Before invoking it, run pwd and pass a path that resolves from there — do NOT prepend packages/<x>/ if your shell is already inside that package. Example failure: running uv run ~/.claude/skills/tasks/tasks.py packages/stamp/prds/foo/tasks.yaml summary from packages/stamp/ fails with FileNotFoundError because it expands to packages/stamp/packages/stamp/prds/foo/tasks.yaml. Use prds/foo/tasks.yaml instead.