Video summary

Up & Running with GitHub Spec Kit #6 - The /tasks Command

Main summary

Key takeaways

Technology

Overview

The video demonstrates how the GitHub Spec Kit generates an actionable task list from a previously written feature plan, specifically using the /tasks command.

What /tasks does (guided tutorial)

  • The /tasks command is run without extra user input, because the detailed technical plan documents were created in earlier steps.
  • Before generating tasks, it:
    • Runs a script to check the current feature branch and the planned documents paths.
    • Outputs relevant information to the terminal so the AI can use it.
  • Then it:
    • Reads the plan documents (if they exist).
    • Uses a tasks template file located in a templates folder.
    • Replaces example tasks in the template with real tasks based on plan content.
    • Applies task generation rules and guidance for ordering tasks.
    • Groups tasks using “AP” so some tasks can run in parallel for the coding agent.
    • Writes the results into a new task file.

Output: generated tasks.md

  • The generated task file is placed under the same specs folder / feature folder.
  • The file includes metadata such as:
    • Import/prerequisites
    • Branch name
    • Total number of tasks (reported as 22)
  • The task list is organized into phases:

Phase 3.1 — Setup

  • Install and configure “shadn” (subtitles suggest “shardn”; likely a UI/component dependency)
  • Install date-fns
  • Configure Tailwind CSS theme with pastel colors

Phase 3.2 — Core implementation (broken into layers)

  • Type definitions and models, including:
    • Goal interface
    • Local storage service
  • UI building blocks, including:
    • Goal card component
    • Goal form
    • Modal component
  • Business logic, including:
    • A custom hook
    • Goal creation logic
    • Completion logic

Phase 3.4 — Integration and layout

  • Connect the created components, hooks, and pages/layouts together.

Phase 3.5 — Polish

  • Add UI polish such as visual highlighting for urgent goals.

Dependencies / ordering

  • The task file includes sequential dependencies so tasks run in the correct order.
  • Each task has an identifier from t01 up to about t22.

Compliance note (testing policy)

  • The tasks explicitly state no automated testing tasks are included.
  • Verification is manual, referencing the “constitution” file for compliance.

Next step mentioned

After generating tasks with /tasks, the video indicates there’s an optional analyze command to run next.

Main speaker / sources

  • Primary source: The video instructor (speaker narrating the steps).
  • Referenced content: The GitHub Spec Kit tooling, especially the /tasks command and its prompt/template files, plus the constitution file.

Original video