Task List Management
Guidelines for managing task lists in Markdown files to track progress on completing a PRD.
Required Companion Skill
Use /interrogate-me when selecting, sequencing, or committing tasks from a PRD task list. Let it stress-test the next task, assumptions, dependencies, risks, and acceptance criteria one question at a time before implementation begins. Capture resulting decisions, risks, or unresolved issues in the task list and "Relevant Files" section as appropriate.
Guardrails
- State the next sub-task, assumptions, and verification command before coding.
- Implement the smallest change that satisfies the active sub-task. Do not add speculative tasks or abstractions.
- Touch only files required by the active sub-task. Mention unrelated cleanup instead of doing it.
- Remove only temporary files and unused code introduced by your own changes.
Task Implementation
- 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:
- When you finish a sub-task, immediately mark it as completed by changing
[ ] to [x].
- If all subtasks underneath a parent task are now
[x], follow this sequence:
- Run the relevant test suite (
pytest, npm test, bin/rails test, etc.).
- Only if tests pass, stage changes with
git add.
- Remove temporary files and temporary code introduced by the task.
- Commit with a descriptive conventional commit message.
- Once all subtasks are completed and committed, mark the parent task as completed.
- Stop after each sub-task and wait for the user's go-ahead.
Task List Maintenance
- Update the task list after significant work.
- Mark finished sub-tasks
[x].
- Mark the parent task
[x] once all its subtasks are [x].
- Add newly discovered tasks only when they are required by the current PRD scope. Otherwise, mention them or add them to a backlog only with user approval.
- Keep "Relevant Files" accurate and include a one-line purpose for each file.
- Before starting work, check which sub-task is next.
- After implementing a sub-task, update the file and pause for user approval.
Install: npx skills add ChristopherAlphonse/calphonse-skills --skill process-task-list
1---2name: process-task-list3description: Guidelines for managing task lists in markdown files to track progress on completing a PRD4---56# Task List Management78Guidelines for managing task lists in Markdown files to track progress on completing a PRD.910## Required Companion Skill1112Use `/interrogate-me` when selecting, sequencing, or committing tasks from a PRD task list. Let it stress-test the next task, assumptions, dependencies, risks, and acceptance criteria one question at a time before implementation begins. Capture resulting decisions, risks, or unresolved issues in the task list and "Relevant Files" section as appropriate.1314## Guardrails1516- State the next sub-task, assumptions, and verification command before coding.17- Implement the smallest change that satisfies the active sub-task. Do not add speculative tasks or abstractions.18- Touch only files required by the active sub-task. Mention unrelated cleanup instead of doing it.19- Remove only temporary files and unused code introduced by your own changes.2021## Task Implementation2223- **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".24- **Completion protocol:**25 1. When you finish a sub-task, immediately mark it as completed by changing `[ ]` to `[x]`.26 2. If all subtasks underneath a parent task are now `[x]`, follow this sequence:27 - Run the relevant test suite (`pytest`, `npm test`, `bin/rails test`, etc.).28 - Only if tests pass, stage changes with `git add`.29 - Remove temporary files and temporary code introduced by the task.30 - Commit with a descriptive conventional commit message.31 3. Once all subtasks are completed and committed, mark the parent task as completed.32- Stop after each sub-task and wait for the user's go-ahead.3334## Task List Maintenance35361. Update the task list after significant work.372. Mark finished sub-tasks `[x]`.383. Mark the parent task `[x]` once all its subtasks are `[x]`.394. Add newly discovered tasks only when they are required by the current PRD scope. Otherwise, mention them or add them to a backlog only with user approval.405. Keep "Relevant Files" accurate and include a one-line purpose for each file.416. Before starting work, check which sub-task is next.427. After implementing a sub-task, update the file and pause for user approval.4344---4546> **Install:** ``npx skills add ChristopherAlphonse/calphonse-skills --skill process-task-list``
ChristopherAlphonse