What is auto_task.create_plan_for_feature?

A planning workflow that breaks a complex feature into a sequence of small, reviewable pull requests, writing a detailed specification for each substantial change. A pull request is a proposed code change for review before it is merged.

Use it to plan multi-step feature work and produce implementation specifications without writing the code itself.

It turns a large request into ordered pieces with clear scope and design decisions, rather than leaving one oversized change to review.

auto_task.create_plan_for_feature — Skill for Claude Code by gpsaggese

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add gpsaggese/helpers --skill auto_task.create_plan_for_feature

Clone the repo

git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/auto_task.create_plan_for_feature/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/auto_task.create_plan_for_feature)

Your own site

<a href="https://agentmods.dev/skills/gpsaggese/helpers/auto_task.create_plan_for_feature"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/auto_task.create_plan_for_feature/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gpsaggese/helpers/auto_task.create_plan_for_feature"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/auto_task.create_plan_for_feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,502 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00016	$0.01502
Opus 5.5	$0.00006	$0.00601
Sonnet 5.5	$0.00003	$0.00300
Haiku 4.5	$0.00002	$0.00150

Measured yesterday against content hash 6589510e99c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

auto_task.create_plan_for_feature scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/auto_task.create_plan_for_feature/SKILL.md · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Goal

Given a request to implement a complex feature, break it into an ordered sequence of small, reviewable PRs
Write a full spec for each PR complex enough to need one
Do not implement any code

Input

The feature/component description, and optionally an existing plan file to extend

When to Use This Skill

Use it when one request needs several independently reviewable changes, and at least one has a design decision worth writing down
If the request fits in one PR, skip to "Write a Spec for a PR" with that PR as the whole request

Workflow

Understand the Request

Read the related code and the existing code in the target directory
If the user references a roadmap file (e.g., plan.<TOPIC>.md or docs/04-plan.md per .claude/skills/project.rules.md), read it for the exact PR scope
- Use the plan ids (e.g., PR_M10) for the PR<NUM> bullets and spec files, per .claude/skills/project.rules.md section "Name the PRs"
Read the architecture doc of the target directory, if one exists
If the problem or solution is unclear, follow .claude/skills/auto_task.rules.md section "Ask for Clarification Before Executing an Unclear Plan" before decomposing

Decompose into PRs

Break the feature into an ordered sequence of small, cohesive PRs, each reviewable and testable alone
Prefer PRs that change whole files over splitting one file's logic across PRs
State each PR's dependencies explicitly
Merge low-risk, low-complexity PRs instead of over-fragmenting

Decide Which PRs Need a Full Spec

A PR needs a full spec if it adds a new interface (class, function, CLI flag), makes a non-obvious design decision, or carries meaningful risk (shared/core code, hard to reverse, many call sites)
Small, mechanical, low-risk PRs (rename, config tweak, adding a test) need no spec: the plan bullet is enough
For each PR that needs a spec, write it with "Write a Spec for a PR" below, using <TOPIC>_PR<NUM> as the topic and the plan file below
- This produces spec.<TOPIC>_PR<NUM>.md

Read the full file on GitHub · 136 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 136 lines · 16 tokens per session scan A 6589510e99c1

Subscribe to this mod's changes

auto_task.create_plan_for_feature is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 1,502 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-06.

Planning Project management

auto_task.create_plan_for_feature next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
auto_task.create_plan_for_featuregpsaggese/helpers	Skill	158	today	Apache-2.0	A	16	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	today	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	99k	today	Apache-2.0	A	19	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
chat-pet-sprite-creationmicrosoft/vscode	Skill	195k	today	MIT	A	53	Claude Code, Codex