handoff

name	handoff
description	Route durable Infiquetra lifecycle artifacts into mission-control prepared issue drafts.

Handoff

Use this when the user wants another team, agent team, or later session to pick up work from an Infiquetra lifecycle artifact.

Boundary

saga owns the handoff moment:

• select the durable source artifact or active pointer;
• infer lifecycle phase and handoff maturity;
• capture why the work is being handed off, blockers, open questions, target team, and target repository when known;
• emit a closed, locally validated saga.handoff-envelope.v1 packet naming artifacts, evidence, risks, and external actions still requiring authority;
• route to mission-control.

mission-control owns the issue artifact:

• issue body sections;
• prepared draft markdown and JSON sidecar;
• readiness checks;
• labels, project fields, board placement, and GitHub mutation;
• create-after-confirmation mutation plan.

Do not copy SDLC issue templates into this skill.

Workflow

1. Prefer an explicit source path or URL from the command arguments.

2. If no source is explicit, inspect .gemini/saga/state.json and durable docs.

3. Build the envelope. The helper validates the closed schema and repository-relative artifact references without performing an external action:

   python3 plugins/saga/scripts/handoff_envelope.py \
     --source docs/plans/example.md \
     --target-team Asgard \
     --target-repo infiquetra-claude-plugins
   

4. If the helper finds no source, ask for one.

5. If multiple durable artifacts are plausible, ask the user to choose.

6. Confirm that artifacts, evidence, risks, and still_unauthorized are non-empty. The last field remains authoritative: an envelope never grants permission to create an issue, update a board, open a PR, merge, or deploy.

7. Route with the envelope's suggested_command, shaped like /issue --prepare --from <source> --maturity <maturity>.

8. Review the prepared issue draft before mutation.

9. Use issue create-prepared only after confirmation.

Maturity

• docs/ideation/ -> idea-ready
• docs/brainstorms/ -> requirements-ready
• docs/specs/ -> requirements-ready
• docs/plans/ or docs/reviews/ -> plan-ready
• docs/work-sessions/ or branch refs -> resume-ready
• explicit preserve/defer language -> deferred-context when the user says execution should wait

Recipient Guidance

Prepared issues must be self-contained for recipients without saga.

When a recipient does have saga, the issue may suggest:

• /plan <issue> for idea-ready or requirements-ready;
• /work <issue> for plan-ready or resume-ready.

Do not suggest /loop for normal team handoff.

Canonical artifact promotion

An Antigravity brain or runtime copy is staging only. Before claiming a durable handoff, promote the packet into docs/handoffs/ with scripts/artifact_promotion.py and bind its promotion receipt to the applicable lifecycle transition. A divergent canonical predecessor is preserved and blocks the handoff until operator adjudication.

Run the executable receipt path before claiming completion. Read $SAGA_PLUGIN_ROOT/references/live-receipt-commands.md for the closed JSON inputs and full flags.

SAGA_PLUGIN_ROOT="${AGY_PLUGIN_ROOT:-$HOME/.gemini/config/plugins/saga}"
test -f "$SAGA_PLUGIN_ROOT/scripts/transition_receipts.py"
test -f "$SAGA_PLUGIN_ROOT/scripts/artifact_promotion.py"