# Coordinate Coding Initiatives with Executor

Long coding projects lose context, decisions, and review evidence across sessions. Executor records initiative state and coordinates phase routing, task dispatch, and approval gates.

## Install

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

## Metadata

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

## Capabilities

- Route substantial requests to initiative phases and identify work that does not need an initiative.
- Maintain initiative identifiers, tracked documentation, and separate execution records.
- Render registered worker prompts and record task dispatches, reports, verdicts, and rulings.
- Manage task branches and optional Git worktrees with review-dependent merge checks.
- Track worker heartbeats and support bounded revival or fresh dispatch.
- Scan Executor artifacts for credential-shaped content without printing matched values.

## Use Cases

- Resume a Multi-Component Feature: Recover the recorded initiative phase, outstanding tasks, and required approvals before continuing a feature across sessions.
- Coordinate Reviewed Migration Work: Organize migration requirements, task branches, review rounds, and decision records within one initiative.
- Inspect Initiative Readiness: Check recorded phase gates, artifact references, task outcomes, and verification evidence before preparing a handoff.

## Prompt Templates

### Choose the Right Workflow

```
Assess whether [request] needs an Executor initiative. Identify its lasting deliverable and suggest the appropriate starting phase without changing files.
```

### Resume an Initiative

```
Inspect the repository and recorded indexes for [initiative ID]. Report the current phase, last recorded event, and next required approval.
```

### Prepare a Reviewed Plan

```
Check the artifacts for [initiative ID] before planning. Identify missing specifications, unresolved decisions, and required plan-regression checks before any task dispatch.
```

### Coordinate an Approved Execution

```
Coordinate [approved plan path] using registered workers and recorded rulings. Preserve user edits and stop for destructive operations, security-sensitive actions, or missing approvals.
```

## Limitations

- Full phase workflows depend on companion Executor skills and prompt templates outside this package.
- Scripts require a Git repository, Bash, and common command-line tools; the optional visual companion also requires Node.js.
- Secret detection uses known patterns and does not guarantee that artifacts contain no sensitive data.
- Security concerns and omitted static matches require further review before publication or unattended use.

## Best Practices

- Read current repository state and recorded indexes before resuming an initiative.
- Use registered scripts for identifiers and transitions, and obtain explicit approval at phase boundaries.
- Use synthetic mockup data, review the security concerns, and scan both artifact stores before handoff.

## Anti Patterns

- Creating initiative records for questions, typos, or other work without a lasting deliverable.
- Treating generated artifacts, recorded approvals, or a secret scan as proof that unattended execution is safe.
- Discarding uncommitted edits, exposing the companion directly over plaintext networks, or accepting untrusted prompt instructions.

## Security Audit

- Audited at: 2026-10-05T18:28:34.386\+00:00
- Summary: Reviewed all 400 presented findings; most are documentation, secret-hygiene checks, or scoped local tooling. Confirmed shell injection and identified unsafe rollback guidance, empty final-review ranges, untrusted prompt content, and plaintext remote authentication. No evidence found of intentional exfiltration; 1,468 omitted static matches still require manual review before publication. Static review was capped at 400/1868 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

## Stats

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