New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Feature Planning

by mhattingpete in mhattingpete/claude-skills-marketplace

Break down feature requests into detailed, implementable plans with clear tasks.

Apache-2.0Auto-check passedAgent Workflows

Install Feature Planning

skills CLI
$ npx skills add mhattingpete/claude-skills-marketplace --skill feature-planning -a claude-code

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

GitHub CLI
$ gh skill install mhattingpete/claude-skills-marketplace feature-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/mhattingpete/claude-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering-workflow-plugin/skills/feature-planning .claude/skills/feature-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
feature-planning
GitHub stars
680
Token cost
~957 tokens
SKILL.md length
324 words
Files
2 (incl. references)
Skills in repo
16
Repo updated
First seen
Licence
Apache-2.0

At a glance

Break down feature requests into detailed, implementable plans with clear tasks.

  • Works in 5 steps: Understand Requirements → Analyze & Design → Create Implementation Plan → …
  • User requests a new feature
  • SKILL.md covers When to Use, Planning Workflow, Best Practices and Integration
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Feature Planning is an agent skill from mhattingpete/claude-skills-marketplace. Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/planning-best-practices.md`).

It sits in Agent Workflows, covering Planning. The repository describes itself as: Claude Code Skills for software engineering workflows - Git automation, testing, and code review. The licence is Apache-2.0.

When your agent uses it

  • User requests a new feature
  • Tasks that involve Planning

Example prompts

  • “/feature-planning”

Workflow steps

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

  1. Understand Requirements
  2. Analyze & Design
  3. Create Implementation Plan
  4. Review Plan with User
  5. Execute with plan-implementer

What it can do on your machine

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

Feature Planning loads about 957 tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 42 tokens; SKILL.md has 324 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~957
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.7k

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 mhattingpete/claude-skills-marketplace at commit b5b34bc, republished under its Apache-2.0 licence (© mhattingpete). 324 words, ~957 tokens.

Download SKILL.mdSave it as .claude/skills/feature-planning/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
feature-planning
description
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.

Feature Planning

Systematically analyze feature requests and create detailed, actionable implementation plans.

When to Use

  • Requests new feature ("add user authentication", "build dashboard")
  • Asks for enhancements ("improve performance", "add export")
  • Describes complex multi-step changes
  • Explicitly asks for planning ("plan how to implement X")
  • Provides vague requirements needing clarification

Planning Workflow

1. Understand Requirements

Ask clarifying questions:

  • What problem does this solve?
  • Who are the users?
  • Specific technical constraints?
  • What does success look like?

Explore the codebase: Use Task tool with subagent_type='Explore' and thoroughness='medium' to understand:

  • Existing architecture and patterns
  • Similar features to reference
  • Where new code should live
  • What will be affected
2. Analyze & Design

Identify components:

  • Database changes (models, migrations, schemas)
  • Backend logic (API endpoints, business logic, services)
  • Frontend changes (UI, state, routing)
  • Testing requirements
  • Documentation updates

Consider architecture:

  • Follow existing patterns (check CLAUDE.md)
  • Identify reusable components
  • Plan error handling and edge cases
  • Consider performance implications
  • Think about security and validation

Check dependencies:

  • New packages/libraries needed
  • Compatibility with existing stack
  • Configuration changes required
3. Create Implementation Plan

Break feature into discrete, sequential tasks:

markdown
## Feature: [Feature Name]

### Overview
[Brief description of what will be built and why]

### Architecture Decisions
- [Key decision 1 and rationale]
- [Key decision 2 and rationale]

### Implementation Tasks

#### Task 1: [Component Name]
- **File**: `path/to/file.py:123`
- **Description**: [What needs to be done]
- **Details**:
  - [Specific requirement 1]
  - [Specific requirement 2]
- **Dependencies**: None (or list task numbers)

#### Task 2: [Component Name]
...

### Testing Strategy
- [What types of tests needed]
- [Critical test cases to cover]

### Integration Points
- [How this connects with existing code]
- [Potential impacts on other features]

Include specific references:

  • File paths with line numbers (src/utils/auth.py:45)
  • Existing patterns to follow
  • Relevant documentation
4. Review Plan with User

Confirm:

  • Does this match expectations?
  • Missing requirements?
  • Adjust priorities or approach?
  • Ready to proceed?
5. Execute with plan-implementer

Launch plan-implementer agent for each task:

Task tool with:
- subagent_type: 'plan-implementer'
- description: 'Implement [task name]'
- prompt: Detailed task description from plan

Execution strategy:

  • Implement sequentially (respect dependencies)
  • Verify each task before next
  • Adjust plan if issues discovered
  • Let test-fixing skill handle failures
  • Let git-pushing skill handle commits

Best Practices

Planning:

  • Start broad, then specific
  • Reference existing code patterns
  • Include file paths and line numbers
  • Think through edge cases upfront
  • Keep tasks focused and atomic

Communication:

  • Explain architectural decisions
  • Highlight trade-offs and alternatives
  • Be explicit about assumptions
  • Provide context for future maintainers

Execution:

  • Implement one task at a time
  • Verify before moving forward
  • Keep user informed
  • Adapt based on discoveries

Integration

  • plan-implementer agent: Receives task specs, implements
  • test-fixing skill: Auto-triggered on test failures
  • git-pushing skill: Triggered for commits

© mhattingpete, 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 (references) in engineering-workflow-plugin/skills/feature-planning of mhattingpete/claude-skills-marketplace.

  • SKILL.md
  • references/planning-best-practices.md

Open the folder on GitHubat commit b5b34bc

Compare with similar skills

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

Feature Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Feature Planning this skillmhattingpete/claude-skills-marketplace680—~957Automated 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 mhattingpete/claude-skills-marketplace

All 16 skills in this repo

  • Architecture Diagram Creator

    mhattingpete/claude-skills-marketplace

    Create comprehensive HTML architecture diagrams showing data flows, business objectives, features, technical architecture, and deployment.

    680 GitHub stars~676 tokensUpdated 2 mo ago
    Auto-check passed

  • Code Transfer

    mhattingpete/claude-skills-marketplace

    Transfer code between files with line-based precision. An agent skill from mhattingpete/claude-skills-marketplace.

    680 GitHub stars~1k tokensUpdated 2 mo ago
    Auto-check passed

  • Conversation Analyzer

    mhattingpete/claude-skills-marketplace

    Analyzes your Claude Code conversation history to identify patterns, common mistakes, and opportunities for workflow improvement.

    680 GitHub stars~1k tokensUpdated 2 mo ago
    Auto-check passed

  • Dashboard Creator

    mhattingpete/claude-skills-marketplace

    Create HTML dashboards with KPI metric cards, bar/pie/line charts, progress indicators, and data visualizations.

    680 GitHub stars~489 tokensUpdated 2 mo ago
    Auto-check passed

  • Flowchart Creator

    mhattingpete/claude-skills-marketplace

    Create HTML flowcharts and process diagrams with decision trees, color-coded stages, arrows, and swimlanes.

    680 GitHub stars~518 tokensUpdated 2 mo ago
    Auto-check passed

  • Technical Doc Creator

    mhattingpete/claude-skills-marketplace

    Create HTML technical documentation with code blocks, API workflows, system architecture diagrams, and syntax highlighting.

    680 GitHub stars~604 tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Feature Planning

What does Feature Planning do?

Break down feature requests into detailed, implementable plans with clear tasks. Feature Planning is an agent skill from mhattingpete/claude-skills-marketplace. Break down feature requests into detailed, implementable plans with clear tasks.

When should I use Feature Planning?

Feature Planning fits situations like: user requests a new feature; tasks that involve Planning.

How do I install Feature Planning in Claude Code?

Run `npx skills add mhattingpete/claude-skills-marketplace --skill feature-planning -a claude-code`. Or copy the skill folder (engineering-workflow-plugin/skills/feature-planning in mhattingpete/claude-skills-marketplace) into .claude/skills/feature-planning in your project. Claude Code loads it when a task matches its description.

How do I install Feature Planning in Codex?

Run `npx skills add mhattingpete/claude-skills-marketplace --skill feature-planning -a codex`. Or copy the skill folder (engineering-workflow-plugin/skills/feature-planning in mhattingpete/claude-skills-marketplace) into .agents/skills/feature-planning in your project. Codex loads it when a task matches its description.

Can I use Feature 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 mhattingpete/claude-skills-marketplace --skill feature-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/feature-planning, .gemini/skills/feature-planning, .github/skills/feature-planning and .opencode/skills/feature-planning in your project.

What does Feature Planning need to run?

SKILL.md names no scripts, command-line tools or credentials: Feature Planning is instructions for the agent only.

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

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

About 957 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.

What are the alternatives to Feature Planning?

Skills that share tags, products or a category with Feature 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 Feature Planning?

mhattingpete (a GitHub user) maintains it in mhattingpete/claude-skills-marketplace, which has 680 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on July 25, 2026.

Source: mhattingpete/claude-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.