← ClaudeAtlas

planlisted

Lightweight planning workflow — delegate read-only planning to a Fable subagent, then implement in auto mode after a single go-ahead gate. The middle tier between "just do it" (tiny tasks) and heavyweight superpowers planning (big features). Never enters plan mode, so it sidesteps the plan-mode permission prompts. Use when the user invokes /plan, or wants a plan for a medium-sized task before implementing.
nielsmadan/skills · ★ 0 · AI & Automation · score 75
Install: claude install-skill nielsmadan/skills
<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # Plan (middle tier) Produce a concrete implementation plan for a medium-sized task, then implement it after one approval gate. Deliberately lighter than `superpowers:brainstorming` / `writing-plans` (no spec files, no per-task checkpoints, no multi-agent fan-out) and heavier than just editing — the space where a plan helps but full ceremony is overkill. **This skill IS the planning workflow for this task.** Do not also invoke `brainstorming` — that is the heavyweight path this skill exists to avoid. Two design choices make it work: - **Never enter plan mode / never call `ExitPlanMode`.** Everything runs in the session's normal (auto) mode. This is intentional: it avoids plan mode's read-only permission prompts entirely, and a subagent's own tool calls never prompt you. - **Fable plans, Opus implements.** A single read-only subagent pinned to the Fable model does the exploring and drafts the plan; the main session implements it. The argument is the task. If blank, infer the task from the current conversation. ## Usage ``` /plan add a --json flag to the export command # plan a stated task /plan # plan the task from context /plan --review <task> # plan, then multi-agent review before the gate ``` ## Flags - `--review` — after the plan is drafted, run `review-plan` (multi-agent) on it and fold