plan
/plan
Break down a goal into actionable tasks with dependencies, priorities, and optional specs. Use when the user wants to plan work, decompose a feature, or create a task breakdown.
- Author
- backloghq ↗
- Repository
- backlog ↗
- Licence
- MIT
- Last repository change
- 30.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Break down a goal into actionable tasks with dependencies, priorities, and optional specs. Use when the user wants to plan work, decompose a feature, or create a task breakdown.
Original author description
Break down a goal into actionable tasks with dependencies, priorities, and optional specs. Use when the user wants to plan work, decompose a feature, or create a task breakdown.
How it works
- Process
SKILL.md preview
--- name: plan description: Break down a goal into actionable tasks with dependencies, priorities, and optional specs. Use when the user wants to plan work, decompose a feature, or create a task breakdown. --- # Plan Work Break down the given goal into actionable tasks. The goal is: "$ARGUMENTS" ## Process 1. **Understand the goal** — analyze what "$ARGUMENTS" requires. Read relevant code, configs, and docs in the codebase to understand the current state. 2. **Decompose into tasks** — create a logical breakdown of work items. Each task should be: - Small enough to complete in one focused session - Clear about what "done" looks like - Independent where possible, with explicit dependencies where not 3. **Create tasks** — for each task, use `task_add` with: - A clear, actionable description (start with a verb, max 500 chars — keep it to a one-line summary; longer content goes in step 4) - `project` set to a logical grouping - `priority` based on urgency and importance (H for blockers, M for core work, L for nice-to-have) - `tags` for categorization (e.g., `frontend`, `backend`, `testing`, `docs`) - `depends` to express ordering constraints (use UUIDs from previously created tasks) - `scheduled` if the task shouldn't start until a certain date 4. **Write specs for complex tasks** — for any task that needs detailed requirements or context (anything that wouldn't fit in 500 chars), use `task_doc_write` to attach a markdown document explaining: - What needs to be built - Key technical decisions - Acceptance criteria - Relevant code locations 5. **Present the plan** — show the created tasks in dependency order with their IDs, descriptions, and priorities. Highlight the first task(s) that can be started immediately (not blocked).
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · backloghq/backlog | 90 | MIT |
| mlophez/polix-ai | 100 | Apache-2.0 |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| duronext/jig | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| xoai/sage | 100 | MIT |
| JoDi-27/JoDi-SDD | 100 | MIT |
Database snapshot: 13.11.2026 · package version e4023a32a472 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100rb-planning
Break down work into board cards for ralph-ban orchestration. This skill should be used when the user has a plan, design doc, or clear requirement to decompose into epics and tasks with EARS specs. Triggers on "plan this", "create cards", "break this down", "decompose into… - 90breaking-down-work
Decomposes a goal, feature, epic, or deliverable into a structured task tree (tasks, subtasks, checklists) with dependencies in Astravue. Use when the user wants to break down, decompose, or plan out work, turn an epic or feature into tasks, "split this into tasks", scope a… - 100oma-pm
Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations. - 95work-breakdown
Convert a feature, refactor, or migration objective into work-unit tickets with acceptance checks and dependencies. Use for backlog preparation or ticket creation rather than implementation. - 100milestone-breakdown
Break down the next open milestone from ROADMAP.md into small, actionable, independently testable tasks in PLAN.md. Trigger whenever the user says "break down", "plan tasks", "create tasks", "task breakdown", "decompose milestone", "phase 2", "let's break this down", references… - 100planning-and-task-breakdown
Decompose specs into small, ordered tasks with acceptance criteria and verification steps. Use when you have requirements and need an implementable plan or task list. Triggers: "break down tasks", "implementation plan", "task breakdown", "plan mode".