Skip to content
Back to skills

Agent Plan To Workers

ASecurity

Compile a frozen reviewed plan into deterministic worker packets with dependency waves, ownership, validation, evidence, and result contracts.

  • 18 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 4, 2026
ai-agentsgo

Security analysis

A100/100

Scanned September 4, 2026

npx -y skills add avksp/agent-lifecycle-kit --skill agent-plan-to-workers --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Plan To Workers?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Plan To Workers
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/avksp-agent-plan-to-workers/badge)](https://www.skillsdirectory.com/skills/avksp-agent-plan-to-workers)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-plan-to-workers
description: Compile a frozen reviewed plan into deterministic worker packets with dependency waves, ownership, validation, evidence, and result contracts.
---

# Agent plan to workers

Use this skill after a plan is reviewed and frozen. The task is compilation:
project a frozen plan into worker packets without redesigning it.

## Contract

1. Verify the plan manifest, lock, source revision, plan digest, and review
   verdict.
2. Reject unfrozen, mismatched, or stale plan inputs.
3. Build dependency waves from the frozen DAG.
4. Emit one packet per executable workstream with:
   task id, owner, reviewer, dependencies, goal, planned items, allowed writes,
   forbidden writes, read-only context, validation command ids, evidence ids,
   budget limits, result path, review path, and remediation route.
5. Emit a controller validation descriptor for controller-owned gates.
6. Keep lead-owned integration and shared seams explicit; do not smuggle them
   into worker write sets.
7. Use deterministic ordering and content-addressed packet identity.

## Rules

- Do not change requirements, acceptance criteria, write ownership, or gates.
- Do not add implementation advice that conflicts with the frozen plan.
- Do not include secrets, private keys, credentials, or host-private state.
- Keep packet context minimal: active task, referenced contracts, and exact
  evidence route.
- For compact mode, emit packets that fit the target profile or report a split
  requirement before execution.
- Fail closed if a worker cannot be assigned a complete ownership and evidence
  contract.

## Output

Return:

- packet index with frozen plan identity;
- dependency waves;
- task packet paths and digests;
- controller validation descriptor;
- unresolved compile findings, if any.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.