Skip to content

Instantly share code, notes, and snippets.

@yigitkonur
Created October 29, 2024 20:33
Show Gist options
  • Select an option

  • Save yigitkonur/8e12d3e9683d6d9f73d9fd8fb8cd0fd1 to your computer and use it in GitHub Desktop.

Select an option

Save yigitkonur/8e12d3e9683d6d9f73d9fd8fb8cd0fd1 to your computer and use it in GitHub Desktop.
Best continue prompt after my evals to implement given task, by including multi-round review to make sure everything is completed

Great job, you can continue only by following this steps:

Task Completion Workflow

  1. Review Previous Implementation

    • Examine the prior work to ensure it has been implemented correctly.
  2. Identify Remaining Tasks

    • List out all tasks that are yet to be completed.
  3. Select the Next Task

    • Choose the first task from the remaining list.
  4. Plan and Explain the Task

    • Develop a detailed plan to accomplish the selected task.
    • Provide an in-depth explanation of your approach.
    • Explain which files will impacted by those changes by thinking deeply about project structure and relevant parts that may appear on other files too.
  5. Implement the Task

    • Execute the plan and complete the task.
  6. Prepare for the Next Task

    • After completing the implementation, briefly explain your plan for the next task.
    • Ask for Approval: Include a sentence seeking approval to proceed, such as "Would you like me to proceed with updating the README.md?"

Guidelines:

  • Focus on Functionality: Prioritize completing the task as specified without over-engineering.
  • Skip Non-Essential Steps: Omit testing, monitoring, unnecessary validations, and production-grade best practices (e.g., rate limiting).
  • Sequential Progress: Continue this process until all requested tasks are implemented.
  1. Final Review
    • After all tasks are completed, conduct a general check.
    • Confirm and state that the overall task is done if everything is implemented.

Use emojis to explain features and state of implementation to keep it concise. Always make comprehensive plans before implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment