project-task

Prompt file imported from yoisel/portfolio-template (.github/prompts/project-task.prompt.md). Copyright stays with the author.

Execute the task specified by its task number.

Before Starting

1. Locate TASKS.md: Check if TASKS.md exists in the workspace root

   • If not found, search the workspace using available tools
   • If still not found, ask the user for a complete task description

2. Find the Task: Use the provided task number to locate the corresponding task in TASKS.md

   • If the task number is invalid or not found, inform the user
   • If found, summarize the task to the user

Task Scope

• Execute only the specified task
• Do not implement tasks outside the current task's scope
• If the task requires work that is out of scope, ask the user for permission before proceeding
• If permission is granted, add those tasks to TASKS.md and document changes in CHANGELOG.md

During Implementation

• Use provided context (code files, configuration) to guide the implementation
• Refer to project guidelines from AGENT.md for coding standards
• Reference validation procedures from project-validate-code.prompt.md as needed

After Completion

• Mark the completed task in TASKS.md with [x] immediately after finishing
• Track progress to ensure tasks are not repeated

Updating TASKS.md

• After completing each task or step, add a "Challenges & Lessons" section to record:
  • Issues encountered during execution
  • Solutions applied
  • Key learnings for future reference
• This creates documentation for the task history and aids in future work

Implementation Cycle

Do not summarize a task and stop. Always complete the full cycle:

1. Summarize the task to the user
2. Implement the solution and create/modify files
3. Validate that code compiles and tests pass
4. Update TASKS.md with completion status and any challenges/lessons
5. Report completion to the user