speckit-tasks-zh

User Input

$ARGUMENTS

Outline

1. Setup: Run

   {SCRIPT}

   from the repository root directory and parse the FEATURE_DIR and AVAILABLE_DOCS lists. All paths must be absolute. For single quotes in parameters, such as "I'm Groot", use escape syntax: e.g., 'I'''m Groot' (or use double quotes if possible: "I'm Groot").
2. Load Design Documents: Read from FEATURE_DIR:
   • Required: plan.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)
   • Note: Not all projects have all documents. Generate tasks based on available content.
3. Execute Task Generation Workflow:
   • Load plan.md and extract tech stack, libraries, project structure
   • Load spec.md and extract prioritized user stories (P1, P2, P3, etc.)
   • 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 task setup
   • Generate tasks organized by user stories (see Task Generation Rules below)
   • Generate a dependency graph showing user story completion order
   • Create parallel execution examples for each user story
   • Verify task completeness (each user story has required tasks and can be tested independently)
4. Generate tasks.md: Use

   .specify/templates/tasks-template.md

   as the structure, populate with:
   • Correct feature name from plan.md
   • Phase 1: Setup tasks (project initialization)
   • Phase 2: Foundation tasks (blocking prerequisites)
   • Phase 3+: Each user story in priority order from spec.md
   • Each phase includes: Story goal, independent testing criteria, tests (if required), implementation tasks
   • Final Phase: Polish and cross-cutting concerns
   • All tasks must follow the strict checklist format (see Task Generation Rules below)
   • Exact file path for each task
   • Dependencies section showing story completion order
   • Parallel execution examples for each story
   • Implementation strategy section (MVP-first, incremental delivery)
5. Report: Output the generated tasks.md path and summary:
   • Total number of tasks
   • Number of tasks per user story
   • Identified parallel opportunities
   • Independent testing criteria for each story
   • Suggested MVP scope (usually only User Story 1)
   • Format validation: Confirm all tasks follow the checklist format (checkbox, ID, tags, file path)

Task Generation Rules

Checklist Format (Required)

- [ ] [Task ID] [P?] [Story?] Description with file path

1. Checkbox: Always start with

   - [ ]

   (markdown checkbox)
2. Task ID: Sequential number in execution order (T001, T002, T003...)
3. [P] Tag: Include only if the task can be parallelized (different files, no dependency on incomplete tasks)
4. [Story] Tag: Required only for user story phase tasks
   • Format: [US1], [US2], [US3], etc. (maps to user stories in spec.md)
   • Setup Phase: No story tag
   • Foundation Phase: No story tag
   • User Story Phase: Must have story tag
   • Polish Phase: No story tag
5. Description: Clear action with exact file path

• ✅ Correct:

  - [ ] T001 Create project structure according to implementation plan

• ✅ Correct:

  - [ ] T005 [P] Implement authentication middleware in src/middleware/auth.py

• ✅ Correct:

  - [ ] T012 [P] [US1] Create user model in src/models/user.py

• ✅ Correct:

  - [ ] T014 [US1] Implement UserService in src/services/user_service.py

• ❌ Incorrect:

  - [ ] Create user model

  (missing ID and story tag)
• ❌ Incorrect:

  T001 [US1] Create model

  (missing checkbox)
• ❌ Incorrect:

  - [ ] [US1] Create user model

  (missing task ID)
• ❌ Incorrect:

  - [ ] T001 [US1] Create model

  (missing file path)

Task Organization

1. From User Stories (spec.md) - Primary organization:
   • Each user story (P1, P2, P3...) has its own phase
   • Map all related components to their story:
     • Models required for the story
     • Services required for the story
     • Endpoints/UI required for the story
     • If testing is required: Specific tests for the story
   • Mark story dependencies (most stories should be independent)
2. From Contracts:
   • Map each contract/endpoint → to the user story it serves
   • If testing is required: Each contract → contract test task [P] before implementation in that story's phase
3. From Data Model:
   • Map each entity to the user story that needs it
   • If an entity serves multiple stories: Place in the earliest story or setup phase
   • Relationships → service layer tasks in the appropriate story phase
4. From Setup/Infrastructure:
   • Shared infrastructure → Setup Phase (Phase 1)
   • Foundation/blocking tasks → Foundation Phase (Phase 2)
   • Story-specific setup → within that story's phase

Phase Structure

• Phase 1: Setup (Project Initialization)
• Phase 2: Foundation (Blocking Prerequisites - must be completed before user stories)
• Phase 3+: User stories in priority order (P1, P2, P3...)
  • Within each story: Tests (if required) → Model → Service → Endpoint → Integration
  • Each phase should be a complete, independently testable increment
• Final Phase: Polish and Cross-Cutting Concerns