OpenParable
Skip to content
← Back to skills

Spec Tasks

Productivity
spec-tasks

Spec Tasks is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Generate actionable, dependency-ordered tasks.md organized by user story. Use when user says "/spec-tasks", "create tasks", "generate task list" after /spec-plan to prepare for implementation.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/spec-tasks/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/spec-tasks, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Spec-Tasks

Generate task list organized by user story for implementation.

Prerequisites: plan.md must exist (run /spec-plan first).

Workflow

  1. Setup - Run .specify/scripts/bash/check-prerequisites.sh --json
  2. Load documents - plan.md (required), spec.md, data-model.md, contracts/
  3. Generate tasks - Organized by user story priority
  4. Write tasks.md - Using .specify/templates/tasks-template.md
  5. Report - Task count, parallel opportunities, MVP scope

Task Format

- [ ] [TaskID] [P?] [Story?] Description with file path
ComponentDescription
- [ ]Checkbox (required)
[T001]Sequential ID
[P]Parallelizable (optional)
[US1]User story label (for story phases)

Examples

- [ ] T001 Create project structure per implementation plan
- [ ] T005 [P] Implement auth middleware in src/middleware/auth.py
- [ ] T012 [P] [US1] Create User model in src/models/user.py

Phase Structure

PhasePurpose
Phase 1: SetupProject initialization
Phase 2: FoundationalBlocking prerequisites
Phase 3+: User StoriesOne phase per story (P1, P2, P3...)
Final: PolishCross-cutting concerns

Task Sources

  1. User Stories (spec.md) - Primary organization
  2. Contracts - Map endpoints to stories
  3. Data Model - Map entities to stories
  4. Infrastructure - Setup/foundational tasks

Parallel Rules

  • [P] = Different files, no dependencies
  • Models before services
  • Services before endpoints
  • Tests FAIL before implementation (if TDD)

Implementation Strategy

MVP First

  1. Setup → Foundational → User Story 1
  2. Test US1 independently
  3. Deploy/demo

Incremental

  1. Add each story independently
  2. Test and deploy each increment

Next Steps

After /spec-tasks:

  • /spec-analyze - Check consistency
  • /spec-implement - Execute tasks