← ClaudeAtlas

agent-planslisted

Manages a FIFO queue of markdown plan files in docs/plans/ (or a custom directory) to coordinate work between humans and agents. Use this skill whenever the user says "work on the next plan", "execute the next task", "check the plans", "what's next to do", or whenever you need to pick up a task from a structured plan queue. Each plan goes through the states pending → review → approved → completed, keeping humans in control of every step.
josbert-m/skills · ★ 0 · AI & Automation · score 61
Install: claude install-skill josbert-m/skills
# Agent Plans A FIFO plan queue system where humans write instructions and agents plan, execute, and report back — one task at a time. ## Overview of the flow ``` pending → (agent adds ## Task) → review → (human approves) → approved → (agent executes) → completed ``` Humans write `## Instructions`. Agents write `## Task` and `## Execution`. Humans stay in control at every handoff. ## Step 1 — Find the next plan Run the helper script (path relative to the skill root): ```bash node scripts/plan.js next # Custom directory: node scripts/plan.js next --dir path/to/plans ``` The script returns JSON. Parse the `action` field to know what to do: | `action` | Meaning | |-------------|-------------------------------------------------------| | `"execute"` | An `approved` plan is ready — go work on it | | `"plan"` | A `pending` plan needs a `## Task` written | | `"none"` | Nothing to do — tell the user | The script also returns `filePath` — the absolute path to the target file. Always use it. ## Step 2a — If action is `"execute"` (approved plan) 1. Read the file at `filePath` 2. Read the `## Task` section carefully — this is what you must do 3. Do the work 4. Update the file: - Change `status: approved` → `status: completed` in the YAML frontmatter - Append a `## Execution` section at the end, summarizing what you did (be brief and precise — this is for the hu