Task Generation

This skill provides comprehensive rules and requirements for generating structured development tasks from Product Requirements Documents (PRDs).

Required Task Fields

Every task MUST have all of these fields:

id: Sequential integer starting from 1
description: Specific, actionable task description with file paths and technical details
success_criteria: Array of 3-7 specific, testable acceptance criteria (MANDATORY - DO NOT SKIP)
dependencies: Array of task IDs this task depends on (use empty array [] if none)
suggested_role: One of "backend", "frontend-ui", or "frontend-logic"
priority: Integer 1-100 (1 = highest priority/critical path, 100 = nice-to-have)

CRITICAL: Task descriptions MUST be in user story format: "As a [role], I need/want [capability] so [benefit]"