Creates phase-based feature plans with quality gates and incremental delivery structure.

No licenceAuto-check passedTesting & QA

Install Feature Planner

skills CLI
$ npx skills add serendipity1004/cc-feature-implementer --skill feature-planner -a claude-code

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

GitHub CLI
$ gh skill install serendipity1004/cc-feature-implementer feature-planner --agent claude-code

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

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
feature-planner
GitHub stars
176
Token cost
~2.4k tokens
SKILL.md length
908 words
Files
2
Skills in repo
1
Repo updated
First seen
Licence
None found

At a glance

Creates phase-based feature plans with quality gates and incremental delivery structure.

  • Works in 5 steps: Requirements Analysis → Phase Breakdown with TDD Integration → Plan Document Creation → …
  • Planning features
  • SKILL.md covers Purpose, Planning Workflow, Quality Gate Standards and Progress Tracking Protocol, plus 5 more sections
  • Calls go, jest and pytest

What it does

Feature Planner is an agent skill from serendipity1004/cc-feature-implementer. Creates phase-based feature plans with quality gates and incremental delivery structure. Use when planning features, organizing work, breaking down tasks, creating roadmaps, or structuring development strategy. Keywords: plan, planning, phases, breakdown, strategy, roadmap, organize, structure, outline.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `plan-template.md`).

It sits in Testing & QA, covering Quality gates and Test-driven development.

When your agent uses it

  • Planning features
  • Organizing work
  • Breaking down tasks
  • Creating roadmaps

Example prompts

  • “Use the feature-planner skill to create phase-based feature plans with quality gates and incremental delivery structure”
  • “/feature-planner”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Requirements Analysis
  2. Phase Breakdown with TDD Integration
  3. Plan Document Creation
  4. User Approval
  5. Document Generation

What it can do on your machine

Read from SKILL.md and the folder at commit 171f59d. 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:

    • go
    • jest
    • pytest
    • mvn
    • gradle
    • dotnet
    • bundle

    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

Feature Planner loads about 2.4k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 908 words of instructions outside code blocks.

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

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 908 words (~2,394 tokens).

name
feature-planner

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in the repository root of serendipity1004/cc-feature-implementer.

  • SKILL.md
  • plan-template.md

Open the folder on GitHubat commit 171f59d

Compare with similar skills

Feature Planner 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.

Feature Planner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Feature Planner this skillserendipity1004/cc-feature-implementer176—~2.4kAutomated safety check: PassNone
Long Task Worksuriyel/longtaskforagent177—~7.1kAutomated safety check: NotesNone
Long Task Qualitysuriyel/longtaskforagent177—~934Automated safety check: PassNone
Shift Left Testingpetrkindlmann/qa-skills168—~6.7kAutomated safety check: PassMIT
Handsontable Test Writing Disciplinehandsontable/handsontable22k—~1.3kAutomated safety check: PassCustom licence
Conductor Workflow Patternswshobson/agents40k9 repos~426Automated safety check: PassMIT

Similar skills

  • Long Task Work

    suriyel/longtaskforagent

    A skill your agent uses when feature-list.json exists - orchestrate features through the full TDD pipeline with quality gates and code review

    177 GitHub stars~7.1k tokensUpdated 3 mo ago
    Testing & QAAuto-check: notes
  • Long Task Quality

    suriyel/longtaskforagent

    Use after TDD cycle in a long-task project - enforces coverage gate, mutation gate, and fresh verification evidence before marking features as passing

    177 GitHub stars~934 tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • Shift Left Testing

    petrkindlmann/qa-skills

    Move quality earlier in the development lifecycle. An agent skill from petrkindlmann/qa-skills.

    168 GitHub stars~6.7k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed
  • Handsontable Test Writing Discipline

    handsontable/handsontable

    Keeps tests honest: write them from the requirement, treat the code as the first suspect when a test is red, and refuse every way of faking a passing run.

    22k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the…

    40k GitHub starsUsed in 9 repos~426 tokens
    DevelopmentAuto-check passed
  • TDD

    pietheinstrengholt/rssmonster

    Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 30 repos~906 tokens
    Testing & QAAuto-check passed

Categories

Questions about Feature Planner

What does Feature Planner do?

Creates phase-based feature plans with quality gates and incremental delivery structure. Feature Planner is an agent skill from serendipity1004/cc-feature-implementer. Creates phase-based feature plans with quality gates and incremental delivery structure.

When should I use Feature Planner?

Feature Planner fits situations like: planning features; organizing work; breaking down tasks; creating roadmaps.

How do I install Feature Planner in Claude Code?

Run `npx skills add serendipity1004/cc-feature-implementer --skill feature-planner -a claude-code`. Or copy the skill folder (the serendipity1004/cc-feature-implementer repository) into .claude/skills/feature-planner in your project. Claude Code loads it when a task matches its description.

How do I install Feature Planner in Codex?

Run `npx skills add serendipity1004/cc-feature-implementer --skill feature-planner -a codex`. Or copy the skill folder (the serendipity1004/cc-feature-implementer repository) into .agents/skills/feature-planner in your project. Codex loads it when a task matches its description.

Can I use Feature Planner 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 serendipity1004/cc-feature-implementer --skill feature-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature-planner, .gemini/skills/feature-planner, .github/skills/feature-planner and .opencode/skills/feature-planner in your project.

What does Feature Planner need to run?

Going by SKILL.md and its folder, Feature Planner needs the command-line tools its instructions call (go, jest, pytest, mvn, gradle and dotnet). Our summary lists: Python 3.

Does Feature Planner 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 Feature Planner 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 Feature Planner use?

No licence was found for Feature Planner or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Feature Planner use?

About 2.4k tokens (SKILL.md is roughly 9.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 Feature Planner?

Skills that share tags, products or a category with Feature Planner: Long Task Work (suriyel/longtaskforagent, 177 stars), Long Task Quality (suriyel/longtaskforagent, 177 stars), Shift Left Testing (petrkindlmann/qa-skills, 168 stars) and Handsontable Test Writing Discipline (handsontable/handsontable, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Feature Planner?

serendipity1004 (a GitHub user) maintains it in serendipity1004/cc-feature-implementer, which has 176 GitHub stars. The repository was last updated on December 23, 2025.

Source: serendipity1004/cc-feature-implementer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.