Please perform a deep audit of our current task to produce a handoff document that gets another agent fully up to speed.
Deliverable:
Create a file named AUDIT_HANDOFF.md at the project root.
Document your current understanding of:
- what we are building
- why we are building it
- the project's telos (ultimate purpose/end-state)
- how we are approaching implementation
- what has been completed so far
- how we define and measure success
- current hypotheses
- what is true (with evidence) vs what is assumed
- what might be wrong
- highest-risk areas
- what we just tried and the outcome
- next hypothesis
- open questions
Required Structure (use these exact section headers)
# Executive Summary
- 5-10 bullets: current project state, trajectory, and key concerns.
# Product Vision and Telos
- What we are building.
- Why it matters.
- Desired end-state if the project fully succeeds.
# Implementation Approach
- Architecture and strategy.
- Key technical decisions and tradeoffs.
- Why this approach was chosen over alternatives.
# Progress So Far
- Completed work.
- In-progress work.
- Deferred/not started work.
- Include concrete references (files, PRs, commits, tests, docs) where possible.
# Success Metrics
- Define primary and secondary metrics.
- For each metric include: baseline, current value (if known), target, and measurement method.
# Hypotheses
- Current main hypothesis.
- Supporting sub-hypotheses.
- What would confirm or falsify each one.
# Evidence vs Assumptions
Include a table with columns:
Claim | Type (Evidence/Assumption) | Source | Confidence (Low/Med/High) | Notes
# Failure Modes and Risk Register
- What could be wrong.
- Highest-risk areas (ranked by impact x likelihood).
- Detection signals and mitigation options for each risk.
# Most Recent Experiment/Attempt
- What was just tried.
- Expected result.
- Actual result.
- Interpretation.
- Artifacts (logs, test outputs, benchmark data, screenshots, etc.).
# Next Hypothesis and Immediate Plan
- Next best hypothesis to test.
- Why this is the highest-leverage next step.
- Step-by-step plan for the next iteration.
# Open Questions
- Unresolved technical, product, and operational questions.
- For each: why it matters, blocking status, and who/what can resolve it.
Quality Bar
- Clearly separate facts, inferences, and assumptions.
- Prefer concrete evidence over narrative.
- Cite sources directly (file paths, line refs, commands, outputs, tickets, PR links).
- Be explicit about uncertainty and confidence.
- Keep it concise but complete; optimize for fast onboarding and auditability.
1---2name: audithandoffdoc3description: Deep audit producing a handoff document to get another agent fully up to speed4---56Please perform a deep audit of our current task to produce a handoff document that gets another agent fully up to speed.78Deliverable:9Create a file named `AUDIT_HANDOFF.md` at the project root.1011Document your current understanding of:12- what we are building13- why we are building it14- the project's telos (ultimate purpose/end-state)15- how we are approaching implementation16- what has been completed so far17- how we define and measure success18- current hypotheses19- what is true (with evidence) vs what is assumed20- what might be wrong21- highest-risk areas22- what we just tried and the outcome23- next hypothesis24- open questions2526Required Structure (use these exact section headers)27281. `# Executive Summary`29- 5-10 bullets: current project state, trajectory, and key concerns.30312. `# Product Vision and Telos`32- What we are building.33- Why it matters.34- Desired end-state if the project fully succeeds.35363. `# Implementation Approach`37- Architecture and strategy.38- Key technical decisions and tradeoffs.39- Why this approach was chosen over alternatives.40414. `# Progress So Far`42- Completed work.43- In-progress work.44- Deferred/not started work.45- Include concrete references (files, PRs, commits, tests, docs) where possible.46475. `# Success Metrics`48- Define primary and secondary metrics.49- For each metric include: baseline, current value (if known), target, and measurement method.50516. `# Hypotheses`52- Current main hypothesis.53- Supporting sub-hypotheses.54- What would confirm or falsify each one.55567. `# Evidence vs Assumptions`57Include a table with columns:58`Claim | Type (Evidence/Assumption) | Source | Confidence (Low/Med/High) | Notes`59608. `# Failure Modes and Risk Register`61- What could be wrong.62- Highest-risk areas (ranked by impact x likelihood).63- Detection signals and mitigation options for each risk.64659. `# Most Recent Experiment/Attempt`66- What was just tried.67- Expected result.68- Actual result.69- Interpretation.70- Artifacts (logs, test outputs, benchmark data, screenshots, etc.).717210. `# Next Hypothesis and Immediate Plan`73- Next best hypothesis to test.74- Why this is the highest-leverage next step.75- Step-by-step plan for the next iteration.767711. `# Open Questions`78- Unresolved technical, product, and operational questions.79- For each: why it matters, blocking status, and who/what can resolve it.8081## Quality Bar8283- Clearly separate **facts**, **inferences**, and **assumptions**.84- Prefer concrete evidence over narrative.85- Cite sources directly (file paths, line refs, commands, outputs, tickets, PR links).86- Be explicit about uncertainty and confidence.87- Keep it concise but complete; optimize for fast onboarding and auditability.
sterlingcrispin