harivansh-afk/iterate-implementation

Iterate Implementation

An implementation plan was implemented and a user has follow-on feedback - it might be a bug, it might be further changes or tweaks, it might be a follow-on feature to implement in the same branch

Steps

1. Read all input files FULLY:

   • Use Read tool WITHOUT limit/offset to read the plan document and any other provided paths
   • If a ticket like ENG-1234 or a task is mentioned, find the task directory: ls .humanlayer/tasks/ | grep -i TEAMID-XXX - you must use Bash(ls | grep) for this as your glob/grep tools don't traverse symlinks
   • ls .humanlayer/tasks/TASKNAME to find all related documents in the task directory
   • Read the YYYY-MM-DD-plan.md to understand the work that was prescribned

2. Understand the current state

   • check the current git diff
   • find the commit that marks the end of implementation
   • read and understand and commits since then - the content of what changed
   • understand what phases of the plan were already implemented - the user might be giving you feedback in the middle of a plan implementation

3. If the user gives any input:

   • DO NOT just accept the correction blindly
   • Read the specific files/directories they mention
   • Verify code examples and file paths are accurate
   • Only proceed once you've verified the facts yourself

4. Clarify the feedback:

   • If user reported a bug: check the database, ask for relevant logs, do whatever is needed to understand what still needs to be done
   • If user requested code changes: Update the specific code examples
   • If there are multiple approaches to fix, ask the user for any clarification
   • If more logs are needed, add logging and ask the user to reproduce issue and share the updated logs

5. Apply the Fix :

   • if the fix is clear or the user has accept one of your proposed solutions, make the changes
   • make the changes
   • run testing and linting

6. Update the user

   • Respond with a summary following the template, including GitHub permalinks, and next steps for verification

<guidance> ## Cloud Permalinks

When you write or edit documents in .humanlayer/tasks/, a cloud permalink is automatically provided in the hook response.

• The permalink appears as additionalContext after Write/Edit/MultiEdit operations
• Use this permalink in your final output for easy navigation
• Example format: http(s)://{DOMAIN}/artifacts/{artifactId}

Markdown Formatting

When writing markdown files that contain code blocks showing other markdown (like README examples or SKILL.md templates), use 4 backticks (````) for the outer fence so inner 3-backtick code blocks don't prematurely close it:

# Example README
## Installation
```bash
npm install example
```

When Iteration is Complete

If the iteration resolves all issues and no further changes are needed:

1. Confirm with the user that implementation is now complete
2. Ask if they want to create a PR
3. If yes, suggest the describe-pr skill:

use the describe-pr skill for .humanlayer/tasks/ENG-XXXX-description

</guidance>