Execute from Goal

Illustrative implementation handoff

The example below is fictional and shows the expected shape of a report. It does not claim that a repository was accessed, a file was changed, or a check was run.

Goal

Add a GET /health endpoint that returns HTTP 200 and an ISO timestamp, following the repository’s existing routing conventions.

Repository findings

• Confirm the server framework and route registration pattern from the actual source before implementation.
• Check whether a health route or timestamp format already exists.
• Identify the project’s relevant test and lint commands from its scripts and contributor guidance.

Implementation outline

1. Add the route in the location used by the existing application.
2. Return a stable JSON shape, for example { "status": "ok", "timestamp": "<ISO timestamp>" }.
3. Register the route using the established application pattern.
4. Add a focused test for the status code and response shape if the project has a suitable test setup.

Verification to report

• Record the exact command run and its actual exit/result.
• If the service was started, record the request used and observed response.
• If a check could not run, explain why; do not report an unrun check as passing.

Handoff

List the actual files changed, summarize the behavior, and note any assumptions or checks that remain. The implementation should be described as complete only after the repository change and its verification have actually occurred.

Huan Dev skill group

Execute from Goal is one of six related skills in the Huan Dev collection: https://github.com/HuanHuanHuanFFF/huan-dev