Implement a Task and Maintain a Handoff File

Ask Codex to implement a specified task while keeping a concise, current handoff document that helps developers verify the work and agents continue it.

Сергей Пименов Republished on Oct 06 0 Bookmarks 0 Copies
Bookmark 0

Example outputs

Example result for Implement a Task and Maintain a Handoff File

Prompt template

Format
Text Parameterized
Inputs
task_requirement (text) · Required project_workspace (code) · Required
Outputs
Implemented_changes (code) Updated_handoff (document)
Implement ${task-requirement} and keep the `HANDOFFmd` file up to date. Record current progress, key decisions and their rationale, important files, verification results, unresolved questions, and next steps. Consider both developer experience (DX) and agent experience (AX). Keep the file concise and limited to current, useful information so I can understand and verify the work and the next agent can continue it. When starting a new task, first read `HANDOFFmd` and compare it with the actual state of the project before proceeding.

Replace the ${…} placeholders with your values before using this prompt. See parameters and defaults below

Parameters

Replace each placeholder with your own value, or use its default when one is provided

${task-requirement} task-requirement Required

What you'll create

A development workflow records useful decisions, files, verification and unresolved work, and checks the handoff against actual project state at the next task start.

Frequently asked questions

Should the handoff accumulate every past detail?

No. It stays concise and limited to current useful information.

Comments

Tried this prompt? Share what you made, compare results, or ask a question

Up to 4 results. Images up to 2 MB; MP4, WebM, or MOV videos up to 4 MB each