π Project Documentation: Check the documentation files in this directory for project-specific setup instructions and guides. Project Tasks: Check the tasks directory in documentation/tasks for the list of tasks to be completed. Use the CLI commands below to interact with them.
π¨ YOU MUST FOLLOW THIS EXACT WORKFLOW - NO EXCEPTIONS π¨
You MUST start by running this command to see all available tasks:
task-manager list-tasksBefore working on any task, you MUST mark it as started:
task-manager start-task <task_id>After finishing implementation, you MUST mark the task as completed, or cancel if you cannot complete it:
task-manager complete-task <task_id> "Brief description of what was implemented"
# or
task-manager cancel-task <task_id> "Reason for cancellation"π Task Data: Your tasks are organized in the documentation/tasks/ directory:
- Task JSON files contain complete task information
- Use ONLY the
task-managercommands listed above - Follow the mandatory workflow sequence for each task
π For EACH individual task, you MUST follow this sequence:
- π DISCOVER:
task-manager list-tasks(first time only) - π START:
task-manager start-task <task_id>(mark as in progress) - π» IMPLEMENT: Do the actual coding/implementation work
- β
COMPLETE:
task-manager complete-task <task_id> "What was done"(or cancel withtask-manager cancel-task <task_id> "Reason") - π REPEAT: Go to next task (start from step 2)
pending- Ready to work onin_progress- Currently being worked oncompleted- Successfully finishedblocked- Cannot proceed (waiting for dependencies)cancelled- No longer needed
β NEVER skip the task-manager start-task command
β NEVER skip the task-manager complete-task command (use task-manager cancel-task if a task is not planned, not required, or you must stop it)
β NEVER work on multiple tasks simultaneously
β
ALWAYS complete one task fully before starting the next
β
ALWAYS provide completion details in the complete command
β
ALWAYS follow the exact 3-step sequence: list β start β complete (or cancel if not required)