Copycat Handoff

Pack release: 0.3.0.

Turn one approved Copycat decision into a compact handoff that a product owner and a coding agent can share.

In worker mode, execute the provided v1 envelope exactly and return only its receipt.

Use restricted I/O: read only declared artifacts, write only the exact handoff paths, copy dispatched hashes, and run no scripts or hash commands.

In standalone mode, ask for one approved BUILD or VALIDATE result, constraints, and the desired output directory.

Boundary

Read only the dispatched immutable round candidate RESULT.md, portfolio RESULT.md, user constraints, and explicitly allowed evidence links. The candidate outcome must be BUILD or VALIDATE. Copy the run ID, immutable source path, and SHA-256 provenance into every handoff artifact exactly as required by the templates. Preserve evidence classifications and unresolved assumptions; do not reopen market research or silently upgrade confidence.

Write under the exact dispatched <handoff-dir>. Use references/product-brief.md for both outcomes. For BUILD, also use references/build-plan.md. copycat-validation owns the VALIDATION_PLAN.md contract.

Method

1. Extract the decision, target, job, wedge, table stakes, differentiation thesis, originality-gate verdict, evidence, counterevidence, constraints, falsifier, and next action.
2. Create PRODUCT_BRIEF.md as the shared source of truth. Make the scope outcome-oriented and traceable. Separate confirmed facts, inferences, assumptions, and open decisions.
3. For BUILD, create BUILD_PLAN.md around the smallest end-to-end vertical slice: appetite, acceptance scenarios, milestones with exit criteria, dependencies, measurement, release gates, risks, and non-goals. Leave codebase-specific architecture to implementation planning.
4. Cross-check every in-scope item against the product outcome and every build milestone against a measurable exit criterion. Preserve the distinction between table stakes and original product expression; remove unsupported features, substantially identical bundles, cosmetic-only differentiation, and invented technical choices.
5. Mark generated documents draft until the user approves them. End each with only open decisions that change scope, cost, or timing.

Completion

Finish when PRODUCT_BRIEF.md and, for BUILD, BUILD_PLAN.md exist, agree with the source result, contain no unresolved placeholder text, and expose all material assumptions. Return the protocol receipt; never paste the documents into the parent context.