agentsclimarketplace

Audithandoffdoc

Skill sterlingcrispin/claude_slash_commands/audithandoffdoc

slash commands for Clade and Codex

Install
npx -y skills add sterlingcrispin/claude_slash_commands --skill audithandoffdoc

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Deep audit producing a handoff document to get another agent fully up to speed

SKILL.md

2.7 KB, 615 tokens by cl100k_base, as published. Nobody here has run it

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)

  1. # Executive Summary
  • 5-10 bullets: current project state, trajectory, and key concerns.
  1. # Product Vision and Telos
  • What we are building.
  • Why it matters.
  • Desired end-state if the project fully succeeds.
  1. # Implementation Approach
  • Architecture and strategy.
  • Key technical decisions and tradeoffs.
  • Why this approach was chosen over alternatives.
  1. # Progress So Far
  • Completed work.
  • In-progress work.
  • Deferred/not started work.
  • Include concrete references (files, PRs, commits, tests, docs) where possible.
  1. # Success Metrics
  • Define primary and secondary metrics.
  • For each metric include: baseline, current value (if known), target, and measurement method.
  1. # Hypotheses
  • Current main hypothesis.
  • Supporting sub-hypotheses.
  • What would confirm or falsify each one.

  1. # Evidence vs Assumptions Include a table with columns: Claim | Type (Evidence/Assumption) | Source | Confidence (Low/Med/High) | Notes

  2. # 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.
  1. # Most Recent Experiment/Attempt
  • What was just tried.
  • Expected result.
  • Actual result.
  • Interpretation.
  • Artifacts (logs, test outputs, benchmark data, screenshots, etc.).
  1. # 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.
  1. # 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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,970. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.