Agent skill

Dev Planning

by codeaholicguy in codeaholicguy/ai-devkit

AI DevKit · Planning phase guidance for creating and reconciling feature task plans.

Apache-2.0Auto-check passedAgent Workflows

Install Dev Planning

skills CLI
$ npx skills add codeaholicguy/ai-devkit --skill dev-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install codeaholicguy/ai-devkit dev-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dev-planning .claude/skills/dev-planning && rm -rf skills-src

Use ~/.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/

Facts

Skill name
dev-planning
GitHub stars
1.6k
Token cost
~826 tokens
SKILL.md length
425 words
Files
2
Skills in repo
28
Repo updated
First seen
Licence
Apache-2.0

At a glance

AI DevKit · Planning phase guidance for creating and reconciling feature task plans.

  • Works in 5 steps: Run npx ai-devkit@latest lint before… → If working on a named feature, run npx… → Read existing configured planning,… → …
  • The user wants to create an implementation plan
  • SKILL.md covers Phase Contract, Create Initial Plan and Update Planning
  • Calls npx

What it does

Dev Planning is an agent skill from codeaholicguy/ai-devkit. AI DevKit · Planning phase guidance for creating and reconciling feature task plans. Use when the user wants to create an implementation plan, update planning docs, mark task progress, capture blockers or new tasks, or run dev-lifecycle planning work.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Agent Workflows, covering Planning. The repository describes itself as: The control plane for AI coding agents. The licence is Apache-2.0.

When your agent uses it

  • The user wants to create an implementation plan
  • Update planning docs
  • Mark task progress
  • Capture blockers

Example prompts

  • “/dev-planning”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Run npx ai-devkit@latest lint before phase work.
  2. If working on a named feature, run npx ai-devkit@latest lint --feature .
  3. Read existing configured planning, implementation, and testing docs before changes. Resolve paths through lint --feature instead of…
  4. Keep task creation and updates traceable to requirements, design, testing scenarios, completed work, blockers, or newly discovered scope.
  5. If parent dev-lifecycle established usable task tracing, emit planning phase, progress, blocker/scope, and next-step events per task.

What it can do on your machine

Read from SKILL.md and the folder at commit 90dcca0. 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

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    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

Dev Planning loads about 826 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 425 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~826

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 codeaholicguy/ai-devkit at commit 90dcca0, republished under its Apache-2.0 licence (© codeaholicguy). 425 words, ~826 tokens.

Download SKILL.mdSave it as .claude/skills/dev-planning/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
dev-planning
description
AI DevKit · Planning phase guidance for creating and reconciling feature task plans. Use when the user wants to create an implementation plan, update planning docs, mark task progress, capture blockers or new tasks, or run dev-lifecycle planning work.

Dev Planning

Run planning creation and reconciliation for configured AI docs features. Before changing docs, propose the concrete plan for this phase and wait for user approval unless the user already approved the exact phase plan.

Phase Contract

  1. Run npx ai-devkit@latest lint before phase work.
  2. If working on a named feature, run npx ai-devkit@latest lint --feature <name>.
  3. Read existing configured planning, implementation, and testing docs before changes. Resolve paths through lint --feature instead of assuming docs/ai.
  4. Keep task creation and updates traceable to requirements, design, testing scenarios, completed work, blockers, or newly discovered scope.
  5. If parent dev-lifecycle established usable task tracing, emit planning phase, progress, blocker/scope, and next-step events per task.

Create Initial Plan

Use for Phase 4 after requirements, design, and initial testing docs exist.

  1. Run npx ai-devkit@latest lint --feature <name> and identify the planning doc path it validates. If docs init-feature just ran, use the returned planning path as authoritative.
  2. Read requirements, design, and testing docs for the feature.
  3. Convert goals, user stories, design components, API/data changes, migration needs, and testing scenarios into implementation tasks.
  4. Group tasks by milestone or logical sequence.
  5. For each task, include outcome, dependencies, validation evidence, and related testing scenarios.
  6. Verify every test-plan scenario has at least one implementation task.
  7. Add risks, blockers, sequencing notes, and likely follow-up checks.
  8. Update the planning doc with the initial ordered task list.
  9. If task tracing is available, record plan progress and next implementation step per task.

Next: dev-implementation.

Show full SKILL.md (170 more words)Show less

Update Planning

Use for Phase 6. Auto-trigger this phase after completing any task in dev-implementation.

  1. Run npx ai-devkit@latest lint --feature <name> and reconcile the planning doc path it validates. If manual path resolution is unavoidable, first resolve .ai-devkit.json paths.docs, falling back to docs/ai.
  2. If continuing from implementation, carry forward existing context. Otherwise ask for feature name, completed tasks, new tasks, blockers, and planning doc path.
  3. Review existing milestones, sequencing, dependencies, and outstanding tasks.
  4. Reconcile each task: mark status as done, in-progress, blocked, or not started; note scope changes; record blockers; capture skipped or added tasks.
  5. Update the planning doc with the current status checklist.
  6. Suggest the next 2-3 actionable tasks, risky areas, and coordination needed.
  7. If task tracing is available, record completed/blocked/new tasks, blockers, and next action per task.
  8. Write a summary paragraph for the planning doc covering progress, risks, upcoming focus, and scope changes.

Next: if tasks remain, return to dev-implementation. If all done, run implementation verification before testing and review.

© codeaholicguy, 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

SKILL.md and 1 other file in skills/dev-planning of codeaholicguy/ai-devkit.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 90dcca0

Compare with similar skills

Dev Planning 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.

Dev Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dev Planning this skillcodeaholicguy/ai-devkit1.6k—~826Automated safety check: PassApache-2.0
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Interview Meaddyosmani/agent-skills103k6 repos~3.8kAutomated safety check: PassMIT
OpenSpec Guided OnboardingFission-AI/OpenSpec71k1 repos~4.5kAutomated safety check: PassMIT
Writing Plansgeeksblabla/stateofdev.ma16357 repos~661Automated safety check: PassNone
Subagent Driven DevelopmentAsvarox/allkaraoke26137 repos~1.2kAutomated safety check: PassNone

Similar skills

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Interview Me

    addyosmani/agent-skills

    Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.

    103k GitHub starsUsed in 6 repos~3.8k tokens
    Agent WorkflowsAuto-check passed
  • OpenSpec Guided Onboarding

    Fission-AI/OpenSpec

    Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.

    71k GitHub starsUsed in 1 repo~4.5k tokens
    Agent WorkflowsAuto-check passed
  • Writing Plans

    geeksblabla/stateofdev.ma

    A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…

    163 GitHub starsUsed in 57 repos~661 tokens
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 37 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Planning With Files

    jd-opensource/JoySafeter

    Implements Manus-style file-based planning for complex tasks.

    313 GitHub starsUsed in 19 repos~1.8k tokens
    Agent WorkflowsAuto-check: notes

More from codeaholicguy/ai-devkit

All 28 skills in this repo
  • Agent Management

    codeaholicguy/ai-devkit

    AI DevKit · Manage running AI agents with ai-devkit agent commands.

    1.6k GitHub stars~558 tokensUpdated today
    Auto-check passed
  • Dev Lifecycle

    codeaholicguy/ai-devkit

    AI DevKit · Orchestrator for structured SDLC phase skills. An agent skill from codeaholicguy/ai-devkit.

    1.6k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Task

    codeaholicguy/ai-devkit

    AI DevKit · Track dev-lifecycle / structured-debug progress on a durable task with the ai-devkit task CLI.

    1.6k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Simplify Implementation

    codeaholicguy/ai-devkit

    AI DevKit · Analyze and simplify existing implementations to reduce complexity, improve maintainability, and enhance scalability.

    1.6k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Agent Communication

    codeaholicguy/ai-devkit

    AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send.

    1.6k GitHub stars~321 tokensUpdated today
    Auto-check passed
  • Technical Writer

    codeaholicguy/ai-devkit

    AI DevKit · Review and improve documentation for novice users.

    1.6k GitHub stars~431 tokensUpdated today
    Auto-check passed

Categories

Questions about Dev Planning

What does Dev Planning do?

AI DevKit · Planning phase guidance for creating and reconciling feature task plans. Dev Planning is an agent skill from codeaholicguy/ai-devkit. AI DevKit · Planning phase guidance for creating and reconciling feature task plans.

When should I use Dev Planning?

Dev Planning fits situations like: the user wants to create an implementation plan; update planning docs; mark task progress; capture blockers.

How do I install Dev Planning in Claude Code?

Run `npx skills add codeaholicguy/ai-devkit --skill dev-planning -a claude-code`. Or copy the skill folder (skills/dev-planning in codeaholicguy/ai-devkit) into .claude/skills/dev-planning in your project. Claude Code loads it when a task matches its description.

How do I install Dev Planning in Codex?

Run `npx skills add codeaholicguy/ai-devkit --skill dev-planning -a codex`. Or copy the skill folder (skills/dev-planning in codeaholicguy/ai-devkit) into .agents/skills/dev-planning in your project. Codex loads it when a task matches its description.

Can I use Dev Planning 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 codeaholicguy/ai-devkit --skill dev-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-planning, .gemini/skills/dev-planning, .github/skills/dev-planning and .opencode/skills/dev-planning in your project.

What does Dev Planning need to run?

Going by SKILL.md and its folder, Dev Planning needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Dev Planning access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Dev Planning 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 Dev Planning use?

Dev Planning 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 Dev Planning use?

About 826 tokens (SKILL.md is roughly 3.3k 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 Dev Planning?

Skills that share tags, products or a category with Dev Planning: Executing Plans Inline (obra/superpowers, 297k stars), Interview Me (addyosmani/agent-skills, 103k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dev Planning?

codeaholicguy (a GitHub user) maintains it in codeaholicguy/ai-devkit, which has 1,643 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 9, 2026.

Source: codeaholicguy/ai-devkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.