rainbow.taskify

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

IMPORTANT: Automatically generate a 'docs:' prefixed git commit message (e.g., 'docs: add implementation tasks for feature-name') and commit tasks.md upon completion.

1. Setup: Run .rainbow/scripts/bash/check-prerequisites.sh --json from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").

2. Load design documents: Read from FEATURE_DIR:

   • Required: design.md (tech stack, libraries, structure), spec.md (user stories with priorities)
   • Optional: data-model.md (entities), contracts/ (API endpoints), research.md (decisions), quickstart.md (test scenarios)
   • Product-level: docs/architecture.md (if exists - architectural patterns, ADRs, deployment architecture)
   • Note: Not all projects have all documents. Generate tasks based on what's available.

3. Execute task generation workflow:

   • Load design.md and extract tech stack, libraries, project structure
   • Load spec.md and extract user stories with their priorities (P1, P2, P3, etc.)
   • If docs/architecture.md exists: Extract architectural patterns, deployment requirements, and ADRs relevant to implementation
   • If data-model.md exists: Extract entities and map to user stories
   • If contracts/ exists: Map endpoints to user stories
   • If research.md exists: Extract decisions for setup tasks
   • Generate tasks organized by user story (see Task Generation Rules below)
   • Generate dependency graph showing user story completion order
   • Create parallel execution examples per user story
   • Validate task completeness (each user story has all needed tasks, independently testable)
   • Ensure tasks align with architectural decisions and patterns from architecture.md (if available)

4. Generate tasks.md: Use .rainbow.rainbow/templates/tasks-template.md as structure, fill with:

   • Correct feature name from design.md
   • Phase 1: Setup tasks (project initialization, aligned with deployment architecture if defined)
   • Phase 2: Foundational tasks (blocking prerequisites for all user stories, following architectural patterns)
   • Phase 3+: One phase per user story (in priority order from spec.md)
   • Each phase includes: story goal, independent test criteria, tests (if requested), implementation tasks
   • Final Phase: Polish & cross-cutting concerns
   • All tasks must follow the strict checklist format (see Task Generation Rules below)
   • Clear file paths for each task (following code organization from architecture.md if available)
   • Dependencies section showing story completion order
   • Parallel execution examples per story
   • Implementation strategy section (MVP first, incremental delivery)
   • Architecture alignment notes (if architecture.md exists)