task-management

name	Task Management
description	Generate implementation task lists from requirements, then process them one at a time with completion tracking and commit protocols.

Task Management

This skill covers two workflows: generating task lists from requirements, and processing task lists one sub-task at a time.

Workflows

1. Generate Tasks - Create a detailed task list from user requirements. See references/generate-tasks.md.
2. Process Task List - Work through tasks one at a time with completion tracking. See references/process-task-list.md.

---

Generate Tasks

Goal

Create a detailed, step-by-step task list in Markdown format based on user requirements, feature requests, or existing documentation. The task list should guide a developer through implementation.

Output

• Format: Markdown (.md)
• Location: /tasks/
• Filename: tasks-[feature-name].md

Process

1. Receive requirements: The user provides a feature request, task description, or points to existing documentation.
2. Analyze requirements: Analyze the functional requirements, user needs, and implementation scope.
3. Phase 1: Generate parent tasks: Create the main high-level tasks. Always include task 0.0 "Create feature branch" as the first task unless the user says otherwise. Present these to the user and say: "I have generated the high-level tasks based on your requirements. Ready to generate the sub-tasks? Respond with 'Go' to proceed."
4. Wait for confirmation: Pause and wait for the user to respond with "Go".
5. Phase 2: Generate sub-tasks: Break down each parent task into smaller, actionable sub-tasks.
6. Identify relevant files: List potential files that will need to be created or modified.
7. Generate final output: Combine parent tasks, sub-tasks, relevant files, and notes into the final Markdown structure.
8. Save task list: Save as tasks-[feature-name].md in the /tasks/ directory.

For full output format details, see references/generate-tasks.md.

Target audience

Assume the primary reader is a junior developer. Requirements should be explicit and unambiguous.

---

Process Task List

Goal

Manage task lists in markdown files to track progress on completing a PRD.

Task implementation rules

• One sub-task at a time: Do NOT start the next sub-task until you ask the user for permission and they say "yes" or "y".
• Completion protocol:
  1. When you finish a sub-task, immediately mark it as completed by changing [ ] to [x].
  2. If all subtasks underneath a parent task are now [x], follow this sequence:
     • Run the full test suite
     • Only if all tests pass: stage changes
     • Clean up any temporary files and temporary code before committing
     • Commit with a descriptive message using conventional commit format (feat:, fix:, refactor:, etc.) that summarizes what was accomplished, lists key changes, and references the task number and PRD context
  3. Once all subtasks are marked completed and changes have been committed, mark the parent task as completed.
• Stop after each sub-task and wait for the user's go-ahead.

Task list maintenance

1. Update the task list as you work:

   • Mark tasks and subtasks as completed ([x]) per the protocol above.
   • Add new tasks as they emerge.

2. Maintain the "Relevant Files" section:

   • List every file created or modified.
   • Give each file a one-line description of its purpose.

Agent instructions

When working with task lists, the agent must:

1. Regularly update the task list file after finishing any significant work.
2. Follow the completion protocol.
3. Add newly discovered tasks.
4. Keep "Relevant Files" accurate and up to date.
5. Before starting work, check which sub-task is next.
6. After completing a sub-task, update the file and then pause for user approval.

Follow the writing standards in _shared/writing-standards.md for all outputs.