{
  "schema_version": "ai_bible_commentary_prompt_json_v3_restored_order",
  "id": "ai-project-handoff-prompt",
  "title": "AI Project Handoff Prompt",
  "menuTitle": "AI Project Handoff Prompt",
  "group": "research",
  "group_label": "RESEARCH",
  "position": 29,
  "canonical_page_url": "https://ai-bible-commentary.com/prompts-library/#ai-project-handoff-prompt",
  "source_prompt_file": "prompts/ai-project-handoff-prompt.md",
  "prompt_text": "AI Chat Project Handoff Prompt\n\nI need a complete operational handoff for starting a new chat on this project.\n\nDo not give me only documentation.\nInclude every required working artifact, especially the latest live workbook/data files, current checkpoint bundles, manifests, prompts, protocols, scripts, wrappers, schemas, QA reports, export folders, upload packages, and any files a new chat would need to continue safely without reconstructing state.\n\nTreat this as a fresh operator handoff: assume the next chat knows nothing and only has the files you give me now.\n\nYour job is to produce:\n\n1. The handoff documents.\n2. The minimum required file set.\n3. The full recommended file set.\n4. The latest live workbook / primary editable file.\n5. The final export/upload artifacts.\n6. The current checkpoint bundle.\n7. All prompts, schemas, Python scripts, PowerShell wrappers, manifests, and protocols needed to continue.\n8. The exact upload order for the new chat.\n9. A starter prompt for the new chat.\n10. A manifest of every file you are giving me, with one-line purpose for each.\n11. An explicit list of critical files whose omission would make the handoff unsafe or incomplete.\n12. A known-problems / do-not-repeat-errors document.\n13. If the next logical step is a new wave, a clearly separated next-wave transition scaffold.\n\nHandoff failure conditions:\n\nThe handoff is not complete unless the primary editable workbook / primary working file is included as a direct downloadable artifact, or you explicitly tell me it is impossible because it exists only on my local computer and you give me a tested local collector script to gather it.\n\nDo not call a ZIP/package a “complete handoff” unless it actually contains the primary workbook, live output/export files, checkpoint folders, scripts, prompts, schemas, manifests, and operator-state files needed to restart.\n\nIf you provide a collector script instead of the actual files, clearly label the package as a “local handoff builder,” not the final handoff. Tell me exactly where to place it, exactly how to run it, and exactly what final ZIP it should create. The final ZIP must then be treated as the real handoff, not the builder package.\n\nBefore finalizing, open/audit the ZIP contents and explicitly confirm that the primary workbook is inside the ZIP. If it is not inside, say the handoff has failed and do not present it as complete.\n\nNext-wave transition requirement:\n\nIf the next logical step is a new wave, include a separate next-wave transition scaffold. Do not leave the next chat guessing whether old wave scripts should be reused.\n\nThe handoff must clearly separate:\n\n1. Completed-wave historical artifacts.\n2. Current primary editable files.\n3. Next-wave starter artifacts.\n\nIf scripts, wrappers, output folders, or manifests are copied forward for the next wave, provide renamed next-wave versions and scan them for stale references to prior waves. Include the scan report. Do not mutate the historical completed-wave files in place.\n\nIf next-wave files cannot be safely generated yet because a new seed workbook or row scope is needed, state that plainly and include a “next-wave preparation checklist” instead of pretending the next wave is ready.\n\nRequired artifact audit before final answer:\n\nBefore giving me the final handoff answer, perform and report an artifact audit with these categories:\n\n1. Primary editable file included?\n2. Latest live workbook/data files included?\n3. Final export/upload package included?\n4. Final checkpoint bundle included?\n5. Prompts included?\n6. Schemas included?\n7. Python scripts included?\n8. PowerShell wrappers included?\n9. Operator-state/checkpoint folder included?\n10. QA/audit/verification reports included?\n11. Sitemap/export manifests included?\n12. New-chat starter prompt included?\n13. Next-wave transition scaffold included, if applicable?\n14. Known-bad patterns / errors-to-avoid document included?\n15. Exact upload order included?\n\nFor each category, answer INCLUDED / NOT NEEDED / MISSING. If any required category is MISSING, do not call the handoff complete.\n\nBefore finishing, do a missing-critical-artifact check and explicitly answer:\n\n1. What is the current primary working file?\n2. Have you included it as a direct download inside the final handoff ZIP?\n3. What file would most damage continuity if omitted?\n4. Is the package a final complete handoff, or only a local handoff builder?\n5. If it is a local handoff builder, what exact command creates the real final ZIP?\n6. Is the next-wave scaffold included, if applicable?\n7. Have all copied next-wave files been renamed and scanned for stale prior-wave references?\n8. Is anything still missing for a safe restart in a new chat?\n\nActive next-wave scaffold hard gate:\n\nIf the next logical step is a new wave, create a separate next-wave scaffold. It must not merely copy old scripts. It must rename active script filenames, wrapper filenames, exporter/auditor filenames, internal defaults, output paths, manifest names, sitemap fragment names, workbook defaults, and all wave labels.\n\nBefore presenting the handoff as complete, run a stale-reference scan across both filenames and file contents in all active next-wave folders. The scan must check for prior-wave labels in scripts, wrappers, exporters, auditors, manifests, and defaults.\n\nIf any active next-wave file still contains a prior-wave reference such as Wave003, Wave004, wave003, wave004, wave_003, wave_004, site_export_wave003, site_export_wave004, simple_production_wave_003, simple_production_wave_004, or export_wave_004, the handoff has failed.\n\nInclude the stale-reference scan report. If the scan is nonzero, do not create or present the next-wave ZIP as safe.\n\nDo not assume documentation is enough.\nDo not omit editable operational files.\nDo not make me infer which files matter.\nDo not call the bundle complete if the workbook or other primary working file is missing.\nDo not rely on memory of filenames; inspect the actual current files before packaging.\nDo not carry over known errors from the previous wave into the next wave.\n\nPackage this so I can open a new chat and continue immediately.\n\nAssume that if the current workbook or other primary working file is missing, the handoff has failed.\n\nMake sure you have done a full and complete audit, and included all necessary artifacts. If anything necessary for this project is on my local computer and cannot be directly included by you, explain clearly and simply where it is, how to gather it, and how to verify that the gathered final ZIP is complete.\n\nHard packaging rule:\n\nDo not copy whole working directories into a handoff or next-wave scaffold unless every file type has been explicitly approved. Use a whitelist, not a broad folder copy.\n\nThe package must exclude all generated cache/bytecode/system files, including __pycache__, *.pyc, .pytest_cache, .mypy_cache, .ruff_cache, .DS_Store, Thumbs.db, old transition folders, old scan reports, and stale generated metadata.\n\nBefore presenting a ZIP as complete, inspect the ZIP itself after creation. Scan both filenames and contents. The scan must include all text/code files and must either scan or forbid binary/cache files. Python bytecode files are never allowed in a handoff or starter scaffold.\n\nIf any active next-wave file, filename, metadata file, manifest, default path, exporter/auditor script, or ZIP entry still contains a prior-wave reference, the handoff has failed. Delete the ZIP and report the findings instead of presenting it as usable.",
  "summary": "AI Chat Project Handoff Prompt I need a complete operational handoff for starting a new chat on this project. Do not give me only documentation. Include every required working artifact, especially the latest live workbook/data files, current checkpoint bundles...",
  "date_modified": "2026-05-31",
  "publisher": {
    "name": "AI Bible Commentary",
    "url": "https://ai-bible-commentary.com/"
  }
}