# Prepare Executor Integration and Session Handoffs

Session changes can lose decisions, verification evidence, and unfinished implementation work. This skill guides human-controlled integration, durable pause records, and resumption checked against the current repository.

## Install

```bash
npx skillstore add atri10/executor-handoff
```

## Metadata

- Status: approved
- Slug: atri10-executor-handoff
- Skillstore revision: r1
- Version status: missing
- Tree hash: e99a47913b71949495af2612920496191b3dc872eb11b871c2f0627d16b6af57
- Author: atri10
- GitHub username: atri10
- License: MIT
- Repository: https://github.com/atri10/executor/tree/39ddcfe1d9f3497102622b72aa235fb0770187fe/skills/executor-handoff
- Ref: 6d0b11444384184b7ae743742a7e233a9a705cd9
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/atri10-executor-handoff
- Manifest: https://skillstore.pages.dev/api/skills/atri10-executor-handoff/manifest

## Capabilities

- Collect recorded rulings into a report with decisions, reasons, and costs of being wrong.
- Require secret scanning across both Executor stores before completed-work integration.
- Rerun applicable checks on the current tree and verify the merged result.
- Present human-controlled merge, pull request, and preservation options according to Git workspace state.
- Update initiative phases, lifecycle statuses, and plan registry rows while retaining execution records.
- Record partial progress and resume through ordered document review followed by Git state checks.

## Use Cases

- Close a Verified Initiative: Review decisions and current verification evidence before choosing local integration, a pull request, or branch preservation.
- Pause Unfinished Implementation: Record unfinished tasks, dispatch outcomes, rulings, and uncommitted changes so another session can continue without reconstructing decisions.
- Resume an Existing Initiative: Compare initiative records with the current checkout, identify discrepancies, and establish the next valid phase before editing.

## Prompt Templates

### Check Handoff Readiness

```
Assess whether initiative [ID] is ready for handoff. Report missing prerequisites and observed evidence. Do not merge, push, or delete anything.
```

### Prepare Integration Choices

```
Prepare handoff for initiative [ID]. Report rulings, scan both stores, and rerun applicable checks. Confirm the base branch and await my integration choice.
```

### Pause a Partial Initiative

```
Pause initiative [ID]. Record unfinished tasks, rulings, dispatch outcomes, phase, and uncommitted files. Scan stores and create the session record. Preserve the workspace.
```

### Reconcile and Resume

```
Resume initiative [ID] from ordered records. Compare Git state with recorded progress and report discrepancies. Verify worktree ownership independently. Await approval before integration or deletion.
```

## Limitations

- The package contains instructions only; referenced Executor helpers and their implementations are not included.
- Secret scanning detects credential-shaped content and does not guarantee that every secret is found.
- Repository checks and pull request creation depend on available project and forge tooling.
- Worktree cleanup uses directory names as ownership evidence and requires an independent provenance check before removal.

## Best Practices

- Preserve observed commands and outcomes; report unavailable or unrun checks explicitly.
- Confirm integration choices and base branches with the human; verify worktree creation records and canonical paths before cleanup.
- Report credential findings by file, line, and kind without copying secret values into transcripts.

## Anti Patterns

- Treating earlier test results or stored completion claims as proof of the current checkout.
- Merging, pushing, force-pushing, or discarding work without the required explicit human decision.
- Deleting execution records or assuming a directory name proves permission to remove a worktree.

## Security Audit

- Audited at: 2026-10-05T17:32:35.971\+00:00
- Summary: All 182 static findings are false positives involving Markdown syntax, fixed dependency references, ordinary Git queries, or deletion safeguards. One semantic risk remains: directory names authorize worktree removal without independent ownership evidence. No evidence found of credential exfiltration or prompt injection; referenced helper implementations are outside this audit.

## Stats

- Views: 1
- Downloads: 0
- Favorites: 0
- Popularity score: 0