ULW Plan Workflow
code-yeongyu/oh-my-openagent
Explore-first planning that turns a vague or large request into one decision-complete work plan, written only after your approval and executed by a separate worker.
Breaks work into ordered tasks. An agent skill from abashev/vfs-s3.
Install Planning And Task Breakdown
$ npx skills add abashev/vfs-s3 --skill planning-and-task-breakdown -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install abashev/vfs-s3 planning-and-task-breakdown --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/abashev/vfs-s3.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/planning-and-task-breakdown .claude/skills/planning-and-task-breakdown && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "planning-and-task-breakdown" agent skill from https://github.com/abashev/vfs-s3/tree/17.0/.claude/skills/planning-and-task-breakdown into .claude/skills/planning-and-task-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-and-task-breakdown", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/abashev/vfs-s3/tree/17.0/.claude/skills/planning-and-task-breakdownType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add abashev/vfs-s3 --skill planning-and-task-breakdown -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install abashev/vfs-s3 planning-and-task-breakdown --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/abashev/vfs-s3.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/planning-and-task-breakdown .agents/skills/planning-and-task-breakdown && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "planning-and-task-breakdown" agent skill from https://github.com/abashev/vfs-s3/tree/17.0/.claude/skills/planning-and-task-breakdown into .agents/skills/planning-and-task-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-and-task-breakdown", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add abashev/vfs-s3 --skill planning-and-task-breakdown -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install abashev/vfs-s3 planning-and-task-breakdown --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/abashev/vfs-s3.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/planning-and-task-breakdown .cursor/skills/planning-and-task-breakdown && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "planning-and-task-breakdown" agent skill from https://github.com/abashev/vfs-s3/tree/17.0/.claude/skills/planning-and-task-breakdown into .cursor/skills/planning-and-task-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-and-task-breakdown", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/abashev/vfs-s3.git --path .claude/skills/planning-and-task-breakdown--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add abashev/vfs-s3 --skill planning-and-task-breakdown -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install abashev/vfs-s3 planning-and-task-breakdown --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/abashev/vfs-s3.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/planning-and-task-breakdown .gemini/skills/planning-and-task-breakdown && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "planning-and-task-breakdown" agent skill from https://github.com/abashev/vfs-s3/tree/17.0/.claude/skills/planning-and-task-breakdown into .gemini/skills/planning-and-task-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-and-task-breakdown", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install abashev/vfs-s3 planning-and-task-breakdownInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add abashev/vfs-s3 --skill planning-and-task-breakdown -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/abashev/vfs-s3.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/planning-and-task-breakdown .github/skills/planning-and-task-breakdown && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "planning-and-task-breakdown" agent skill from https://github.com/abashev/vfs-s3/tree/17.0/.claude/skills/planning-and-task-breakdown into .github/skills/planning-and-task-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-and-task-breakdown", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add abashev/vfs-s3 --skill planning-and-task-breakdown -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install abashev/vfs-s3 planning-and-task-breakdown --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/abashev/vfs-s3.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/planning-and-task-breakdown .opencode/skills/planning-and-task-breakdown && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "planning-and-task-breakdown" agent skill from https://github.com/abashev/vfs-s3/tree/17.0/.claude/skills/planning-and-task-breakdown into .opencode/skills/planning-and-task-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-and-task-breakdown", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
planning-and-task-breakdown- GitHub stars
- 106
- Used in
- 8 other repos
- Token cost
- ~1.9k tokens
- SKILL.md length
- 707 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Breaks work into ordered tasks. An agent skill from abashev/vfs-s3.
- Works in 5 steps: Enter Plan Mode → Identify the Dependency Graph → Slice Vertically → …
- You have a spec
- SKILL.md covers Overview, When to Use, The Planning Process and Task Sizing Guidelines, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Planning And Task Breakdown is an agent skill from abashev/vfs-s3. Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Task breakdown and Planning. The repository describes itself as: Amazon S3 driver for Apache commons-vfs (Virtual File System) project. The licence is Apache-2.0.
When your agent uses it
- You have a spec
- Clear requirements and need to break work into implementable tasks
- A task feels too large to start
- You need to estimate scope
Example prompts
- “Use the planning-and-task-breakdown skill to break work into ordered tasks. An agent skill from abashev/vfs-s3”
- “/planning-and-task-breakdown”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit fae1983. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Planning And Task Breakdown loads about 1.9k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 707 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from abashev/vfs-s3 at commit fae1983, republished under its Apache-2.0 licence (© abashev). 707 words, ~1,889 tokens.
Download SKILL.mdSave it as
.claude/skills/planning-and-task-breakdown/SKILL.md (or your agent's skills folder).- name
- planning-and-task-breakdown
- description
- Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
Planning and Task Breakdown
Overview
Decompose work into small, verifiable tasks with explicit acceptance criteria. Good task breakdown is the difference between an agent that completes work reliably and one that produces a tangled mess. Every task should be small enough to implement, test, and verify in a single focused session.
When to Use
- You have a spec and need to break it into implementable units
- A task feels too large or vague to start
- Work needs to be parallelized across multiple agents or sessions
- You need to communicate scope to a human
- The implementation order isn't obvious
When NOT to use: Single-file changes with obvious scope, or when the spec already contains well-defined tasks.
The Planning Process
Step 1: Enter Plan Mode
Before writing any code, operate in read-only mode:
- Read the spec and relevant codebase sections
- Identify existing patterns and conventions
- Map dependencies between components
- Note risks and unknowns
Do NOT write code during planning. The output is a plan document saved to tasks/plan.md and a task list saved to tasks/todo.md, not implementation.
Step 2: Identify the Dependency Graph
Map what depends on what:
Database schema
│
├── API models/types
│ │
│ ├── API endpoints
│ │ │
│ │ └── Frontend API client
│ │ │
│ │ └── UI components
│ │
│ └── Validation logic
│
└── Seed data / migrationsImplementation order follows the dependency graph bottom-up: build foundations first.
Step 3: Slice Vertically
Instead of building all the database, then all the API, then all the UI — build one complete feature path at a time:
Bad (horizontal slicing):
Task 1: Build entire database schema
Task 2: Build all API endpoints
Task 3: Build all UI components
Task 4: Connect everythingGood (vertical slicing):
Task 1: User can create an account (schema + API + UI for registration)
Task 2: User can log in (auth schema + API + UI for login)
Task 3: User can create a task (task schema + API + UI for creation)
Task 4: User can view task list (query + API + UI for list view)Each vertical slice delivers working, testable functionality.
Step 4: Write Tasks
Each task follows this structure:
## Task [N]: [Short descriptive title]
**Description:** One paragraph explaining what this task accomplishes.
**Acceptance criteria:**
- [ ] [Specific, testable condition]
- [ ] [Specific, testable condition]
**Verification:**
- [ ] Tests pass: `npm test -- --grep "feature-name"`
- [ ] Build succeeds: `npm run build`
- [ ] Manual check: [description of what to verify]
**Dependencies:** [Task numbers this depends on, or "None"]
**Files likely touched:**
- `src/path/to/file.ts`
- `tests/path/to/test.ts`
**Estimated scope:** [Small: 1-2 files | Medium: 3-5 files | Large: 5+ files]Step 5: Order and Checkpoint
Arrange tasks so that:
- Dependencies are satisfied (build foundation first)
- Each task leaves the system in a working state
- Verification checkpoints occur after every 2-3 tasks
- High-risk tasks are early (fail fast)
Add explicit checkpoints:
## Checkpoint: After Tasks 1-3
- [ ] All tests pass
- [ ] Application builds without errors
- [ ] Core user flow works end-to-end
- [ ] Review with human before proceedingTask Sizing Guidelines
| Size | Files | Scope | Example |
|---|---|---|---|
| XS | 1 | Single function or config change | Add a validation rule |
| S | 1-2 | One component or endpoint | Add a new API endpoint |
| M | 3-5 | One feature slice | User registration flow |
| L | 5-8 | Multi-component feature | Search with filtering and pagination |
| XL | 8+ | Too large — break it down further | — |
If a task is L or larger, it should be broken into smaller tasks. An agent performs best on S and M tasks.
When to break a task down further:
- It would take more than one focused session (roughly 2+ hours of agent work)
- You cannot describe the acceptance criteria in 3 or fewer bullet points
- It touches two or more independent subsystems (e.g., auth and billing)
- You find yourself writing "and" in the task title (a sign it is two tasks)
Show full SKILL.md (283 more words)Show less
Output Files
- Plan document: Save the implementation plan to
tasks/plan.md. - Task list: Save the checklist-style task list to
tasks/todo.md.
Create the tasks/ directory if it does not exist. These paths are the convention expected by the /build command and other downstream tooling.
Plan Document Template
# Implementation Plan: [Feature/Project Name]
## Overview
[One paragraph summary of what we're building]
## Architecture Decisions
- [Key decision 1 and rationale]
- [Key decision 2 and rationale]
## Task List
### Phase 1: Foundation
- [ ] Task 1: ...
- [ ] Task 2: ...
### Checkpoint: Foundation
- [ ] Tests pass, builds clean
### Phase 2: Core Features
- [ ] Task 3: ...
- [ ] Task 4: ...
### Checkpoint: Core Features
- [ ] End-to-end flow works
### Phase 3: Polish
- [ ] Task 5: ...
- [ ] Task 6: ...
### Checkpoint: Complete
- [ ] All acceptance criteria met
- [ ] Ready for review
## Risks and Mitigations
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk] | [High/Med/Low] | [Strategy] |
## Open Questions
- [Question needing human input]Parallelization Opportunities
When multiple agents or sessions are available:
- Safe to parallelize: Independent feature slices, tests for already-implemented features, documentation
- Must be sequential: Database migrations, shared state changes, dependency chains
- Needs coordination: Features that share an API contract (define the contract first, then parallelize)
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "I'll figure it out as I go" | That's how you end up with a tangled mess and rework. 10 minutes of planning saves hours. |
| "The tasks are obvious" | Write them down anyway. Explicit tasks surface hidden dependencies and forgotten edge cases. |
| "Planning is overhead" | Planning is the task. Implementation without a plan is just typing. |
| "I can hold it all in my head" | Context windows are finite. Written plans survive session boundaries and compaction. |
Red Flags
- Starting implementation without a written task list
- Tasks that say "implement the feature" without acceptance criteria
- No verification steps in the plan
- All tasks are XL-sized
- No checkpoints between tasks
- Dependency order isn't considered
Verification
Before starting implementation, confirm:
- Every task has acceptance criteria
- Every task has a verification step
- Task dependencies are identified and ordered correctly
- No task touches more than ~5 files
- Checkpoints exist between major phases
- The human has reviewed and approved the plan
See Also
Acceptance criteria are per-task and answer "did we build the right thing?". They sit on top of the project-wide Definition of Done, the standing bar every task clears before it counts as done. See references/definition-of-done.md.
© abashev, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/planning-and-task-breakdown of abashev/vfs-s3.
Open the folder on GitHubat commit fae1983
Used in 8 other repositories
We found 12 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 8 other GitHub owners. This page covers the copy in abashev/vfs-s3, which our catalogue first saw on October 7, 2026.
- dzhalaevd/Donatello.agents/skills/planning-and-task-breakdown
- addyosmani/agent-skillsskills/planning-and-task-breakdown
- shashankswe2020-ux/whoop-mcp.github/skills/planning-and-task-breakdown
- xingranya/GitHub-Stars-AI-Toolsskills/planning-and-task-breakdown
- aiskillstore/marketplaceskills/addyosmani/planning-and-task-breakdown
- sickn33/agentic-awesome-skillsskills/planning-and-task-breakdownplugins/agentic-awesome-skills/skills/planning-and-task-breakdown+1 more
- NeverSight/learn-skills.devdata/skills-md/addyosmani/agent-skills/planning-and-task-breakdown
- lingxling/awesome-skills-cnantigravity-awesome-skills/skills/planning-and-task-breakdownantigravity-awesome-skills/plugins/agentic-awesome-skills/skills/planning-and-task-breakdown+1 more
Compare with similar skills
Planning And Task Breakdown next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Planning And Task Breakdown this skillabashev/vfs-s3 | 106 | 8 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| ULW Plan Workflowcode-yeongyu/oh-my-openagent | 70k | — | ~3.9k | Automated safety check: Pass | Custom licence | |
| Ask NavigatorYeachan-Heo/oh-my-claudecode | 40k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Implementation Plan Creatortailcallhq/forgecode | 7.6k | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Harness PlanChachamaru127/claude-code-harness | 3.2k | — | ~3.7k | Automated safety check: Notes | MIT | |
| Plannotator Goal Setupbacknotprop/plannotator | 9.2k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Ask Navigator
Yeachan-Heo/oh-my-claudecode
Charts a foggy effort into a map of decision tickets on the repo's issue tracker and works through them one per session, producing decisions rather than deliverables.
Implementation Plan Creator
tailcallhq/forgecode
Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.
Harness Plan
Chachamaru127/claude-code-harness
Creates and maintains Plans.md task plans with a spec delta, updates task markers and syncs plan progress with the implementation.
Plannotator Goal Setup
backnotprop/plannotator
Guides the agent from a vague objective to a written goal package under goals/, using a confirmed restatement, a browser interview, a fact sheet and a codebase pass.
Ultragoal Multi-Goal Ledger
Yeachan-Heo/gajae-code
Breaks a brief into ordered goals, keeps a durable ledger under .omc/ultragoal and prints handoff text so a Claude /goal run survives session restarts.
More from abashev/vfs-s3
Context Engineering
abashev/vfs-s3
Optimizes agent context setup. An agent skill from abashev/vfs-s3.
Debugging And Error Recovery
abashev/vfs-s3
Guides systematic root-cause debugging. An agent skill from abashev/vfs-s3.
Doubt Driven Development
abashev/vfs-s3
Subjects every non-trivial decision to a fresh-context adversarial review before it stands.
Incremental Implementation
abashev/vfs-s3
Delivers changes incrementally. An agent skill from abashev/vfs-s3.
Spec Driven Development
abashev/vfs-s3
Creates specs before coding. An agent skill from abashev/vfs-s3.
Test Driven Development
abashev/vfs-s3
Drives development with tests. An agent skill from abashev/vfs-s3.
Related
Categories
Questions about Planning And Task Breakdown
What does Planning And Task Breakdown do?
Breaks work into ordered tasks. An agent skill from abashev/vfs-s3. Planning And Task Breakdown is an agent skill from abashev/vfs-s3. Breaks work into ordered tasks.
When should I use Planning And Task Breakdown?
Planning And Task Breakdown fits situations like: you have a spec; clear requirements and need to break work into implementable tasks; A task feels too large to start; you need to estimate scope.
How do I install Planning And Task Breakdown in Claude Code?
Run `npx skills add abashev/vfs-s3 --skill planning-and-task-breakdown -a claude-code`. Or copy the skill folder (.claude/skills/planning-and-task-breakdown in abashev/vfs-s3) into .claude/skills/planning-and-task-breakdown in your project. Claude Code loads it when a task matches its description.
How do I install Planning And Task Breakdown in Codex?
Run `npx skills add abashev/vfs-s3 --skill planning-and-task-breakdown -a codex`. Or copy the skill folder (.claude/skills/planning-and-task-breakdown in abashev/vfs-s3) into .agents/skills/planning-and-task-breakdown in your project. Codex loads it when a task matches its description.
Can I use Planning And Task Breakdown in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add abashev/vfs-s3 --skill planning-and-task-breakdown -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning-and-task-breakdown, .gemini/skills/planning-and-task-breakdown, .github/skills/planning-and-task-breakdown and .opencode/skills/planning-and-task-breakdown in your project.
What does Planning And Task Breakdown need to run?
SKILL.md names no scripts, command-line tools or credentials: Planning And Task Breakdown is instructions for the agent only.
Does Planning And Task Breakdown access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Planning And Task Breakdown safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Planning And Task Breakdown use?
Planning And Task Breakdown is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Planning And Task Breakdown use?
About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Planning And Task Breakdown?
Skills that share tags, products or a category with Planning And Task Breakdown: ULW Plan Workflow (code-yeongyu/oh-my-openagent, 70k stars), Ask Navigator (Yeachan-Heo/oh-my-claudecode, 40k stars), Implementation Plan Creator (tailcallhq/forgecode, 7.6k stars) and Harness Plan (Chachamaru127/claude-code-harness, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Planning And Task Breakdown?
abashev (a GitHub user) maintains it in abashev/vfs-s3, which has 106 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: abashev/vfs-s3 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.