Task List Management

Guidelines for managing task lists in markdown files to track progress on completing a PRD

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:
  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:
  • First: Run the full test suite (pytest, npm test, bin/rails test, etc.)
  • Only if all tests pass: Stage changes (git add .)
  • Clean up: Remove any temporary files and temporary code before committing
  • Commit: Use a descriptive commit message that:
    • Uses conventional commit format (feat:, fix:, refactor:, etc.)
    • Summarizes what was accomplished in the parent task
    • Lists key changes and additions
    • References the task number and PRD context
    • Formats the message as a single-line command using -m flags, e.g.: