create-task-spec

name	create-task-spec
description	Create hyper-detailed task specifications with embedded context, eliminating implementation lookups. This skill should be used for breaking features into implementable tasks with complete architecture references.
acceptance	[{"task_file_created":"Task specification file created in configured location"},{"context_embedded":"All technical context embedded with source references"},{"tasks_defined":"3-15 sequential tasks with validation checkpoints"},{"user_approved":"User reviewed and approved specification"}]
inputs	{"requirement":{"type":"string","required":true,"description":"Feature or requirement to implement"},"priority":{"type":"string","required":false,"description":"Priority level (P0/P1/P2/P3)","default":"P2"}}
outputs	{"task_file":{"type":"string","description":"Path to created task specification file"},"task_id":{"type":"string","description":"Generated task ID (e.g., task-006)"},"task_count":{"type":"number","description":"Number of tasks in breakdown"},"status":{"type":"string","description":"Task status (Draft or Approved)"}}
telemetry	{"emit":"skill.create-task-spec.completed","track":["task_id","task_count","subtask_count","priority","status","duration_ms"]}

Create Task Specification Skill

Purpose

Create hyper-detailed task specifications that embed ALL context needed for implementation, eliminating the need for developers to search for information during coding.

Core Capabilities:

• Requirement gathering and clarification
• Architecture context extraction with source references
• Component analysis (data models, APIs, UI)
• Sequential task breakdown with validation checkpoints
• Self-contained specifications

BMAD Pattern (Key Innovation):

• SM reads PRD + Architecture + Previous task notes
• Creates detailed task spec with embedded context
• Dev reads ONLY task spec (no architecture lookup)
• Result: Context never lost, implementation never blocked

Prerequisites

• Configuration file (.claude/config.yaml) with task settings
• Task template (.claude/templates/task-spec.md)
• Architecture documentation (optional but recommended)
• Project coding standards

---

Workflow

Step 0: Load Configuration and Validate Prerequisites

Action: Load configuration and verify prerequisites.

Execute:

python .claude/skills/bmad-commands/scripts/read_file.py \
  --path .claude/config.yaml \
  --output json

Extract: documentation.architecture, development.alwaysLoadFiles, development.taskLocation, templates.taskSpec

Verify: Task location exists, template exists, determine next task ID

Halt if: Config missing, template missing, cannot determine task ID

See: references/templates.md for configuration format and references/requirements-gathering-guide.md for requirement clarification

---

Step 1: Gather Requirements from User

Action: Clarify requirement, acceptance criteria, and priority.

Ask user:

1. What needs to be implemented?

   • Feature description
   • Problem it solves
   • Primary user/beneficiary

2. What defines "done"?

   • Testable outcomes