Skip to content

Project Packet Builder

Builds a deterministic handoff packet from existing PKM and wiki context, leaving no implicit assumptions for the executing agent.

When to use

  • Following a Go or Conditional Go from /handoff-readiness-assessor.
  • "Build a handoff packet for project X."
  • Before /execution-router.

What you produce

A markdown file at workflow/handoff/packets/<project-slug>-<date>.md populated using /workflow/handoff/templates/handoff-packet.md.

Procedure

  1. Verify Go/Conditional Go — read the latest readiness scoring sheet for the project. Refuse if No-Go.
  2. Pull project record from AnyType: name, owner, objective, acceptance criteria, classification.
  3. Collect dependencies — look up linked Project/Source pages; resolve repos and services.
  4. Determine credential sources — never embed secrets; reference the user-only secret store path or agent-scoped key labels (SPB-02/SPB-03/SPB-04).
  5. Compose verification plan — pull from acceptance criteria + standard test/rollback skeleton.
  6. Defer routing rationale to /execution-router if not already chosen; otherwise capture the chosen runtime + rule(s) matched.
  7. Render the packet to workflow/handoff/packets/<slug>-<date>.md.
  8. Cross-link the packet from the AnyType Project (wiki_index_id).
  9. Verifier handoff — every required section non-empty, no plaintext secrets, no missing dependencies.

Anti-patterns

  • Don't fabricate acceptance criteria. If absent, fail back to the readiness assessor.
  • Don't embed secrets — only references.
  • Don't infer the runtime here; that's /execution-router.

Compatibility

  • Read access to AnyType + agent wiki.
  • Write access only to workflow/handoff/packets/ and the project's wiki_index_id field.
  • No cloud egress for private_sensitive projects.