Plan A Feature
Builds a feature specification from scratch through a relentless, evidence-based interview that walks the design tree decision-by-decision, resolving dependencies as it goes. Use when the user wants to plan, design, scope, specify, or flesh out a new feature, capability, or system behavior before implementation — including requests like "help me plan X", "spec out this feature", "design the Y flow", or "let's figure out what it should do". Explores the codebase, project documentation, coding standards, and ADRs to resolve questions before asking the user, and always offers a recommended answer when questions must be surfaced. Produces a feature-specification.md focused on system behaviors, coordinations, processes, and user interactions — not implementation detail. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not investigate bugs or failures — use investigate. Does not analyze existing architecture — use architectural-analysis. Does not document already-built features — use project-documentation. Does not record architectural decisions — use architectural-decision-record.
Security AStatic scan found no risk patternsHow grading works ›
What this skill does
Plan A Feature is a community-contributed Claude Code skill in the prd-spec sub-category. It ships as a SKILL.md file that Claude Code auto-discovers under ~/.claude/skills/plan-a-feature/ and loads when your prompt matches the skill's trigger.
When to invoke it: Use when the user wants to plan, design, scope, specify, or flesh out a new feature, capability, or system behavior before implementation — including requests like "help me plan X", "spec out this feature", "design the Y flow", or "let's figure out what it should do". Explores the codebase, project documentation, coding standards, and ADRs to resolve questions before asking the user, and always offers a recommended answer when questions must be surfaced.
Who uses this skill
The Plan A Feature Claude Code skill is built for product managers, product designers, and cross-functional teams planning, shipping, and measuring product features. It's part of ClaudSkills (also referred to as Claude Skills or Claude Code Skills) — the open community-curated registry of 211,000+ SKILL.md files for Anthropic's Claude Code agent and the wider Claude ecosystem (Claude API, Claude Agent SDK).
How to install
Free
Manual install (2 steps)
mkdir -p ~/.claude/skills/plan-a-feature
curl -L https://claudskills.com/skills/plan-a-feature/SKILL.md \
-o ~/.claude/skills/plan-a-feature/SKILL.md
Or just download SKILL.md directly and drop it into ~/.claude/skills/plan-a-feature/. Claude Code auto-discovers it on next session.
Skills live at ~/.claude/skills/plan-a-feature/SKILL.md on macOS/Linux, or %USERPROFILE%\.claude\skills\plan-a-feature\SKILL.md on Windows. See the full install guide for step-by-step instructions.
Telegram
📱 Install from your phone or desktop Telegram
Open @claudskills_bot on Telegram, tap Open Desktop App, and the desktop app installs this skill for you. Or share the bot link with a colleague — they get the same one-tap install. Learn more →
Pro
One-click install via the desktop app
The ClaudSkills desktop app installs any skill directly into ~/.claude/skills/ with one click — no terminal required. Pro starts at $9/mo or $149 lifetime.
Pro
For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.
Frequently asked questions
How do I install the Plan A Feature Claude Code skill?
Install via the ClaudSkills desktop app (one click) or copy
SKILL.md from the source repository to
~/.claude/skills/plan-a-feature/SKILL.md and restart Claude Code. Both flows are detailed at
claudskills.com/install/.
What does the Plan A Feature skill do?
Builds a feature specification from scratch through a relentless, evidence-based interview that walks the design tree decision-by-decision, resolving dependencies as it goes. Use when the user wants to plan, design, scope, specify, or flesh out a new feature, capability, or system behavior before implementation — including requests like "help me plan X", "spec out this feature", "design the Y flow", or "let's figure out what it should do". Explores the codebase, project documentation, coding standards, and ADRs to resolve questions before asking the user, and always offers a recommended answer when questions must be surfaced. Produces a feature-specification.md focused on system behaviors, coordinations, processes, and user interactions — not implementation detail. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not investigate bugs or failures — use investigate. Does not analyze existing architecture — use architectural-analysis. Does not document already-built features — use project-documentation. Does not record architectural decisions — use architectural-decision-record.
Is this skill free to install?
Yes. ClaudSkills is an open registry — every skill keeps its source repository's license, and manual install via copy is free. ClaudSkills Pro ($9/mo, $79/yr, or $149 one-time) adds one-click install via the desktop app and a multi-signal Quality Score.
When should I use the Plan A Feature skill?
Use Plan A Feature when your Claude Code task falls under the Product category — specifically in the prd spec area. Claude Code auto-discovers installed skills and invokes the right one based on the task description, so you can also ask Claude directly (e.g. "use Plan A Feature" or describe the task and let Claude pick). Browse related skills at
/category/product/.
What is a Claude Code skill and how does the Plan A Feature skill fit in?
A Claude Code skill is a
SKILL.md file that lives under
~/.claude/skills/<name>/ and tells the Claude Code CLI agent how to perform a specific task (instructions, prompts, allowed tools). Skills are auto-discovered at session start. Plan A Feature is one of 67,000+ skills indexed in the open ClaudSkills catalog, classified under the Product category. Learn more at
/learn/what-is-a-claude-skill/.
Attribution & license
Cite this skill
If you reference this skill in a blog post, paper, or documentation, you can cite it as:
APA
testdouble. (2026). Plan A Feature [Claude Code skill]. ClaudSkills. https://claudskills.com/skills/plan-a-feature/
BibTeX
@misc{plan-a-feature-2026,
author = {testdouble},
title = {Plan A Feature [Claude Code skill]},
year = {2026},
publisher = {ClaudSkills},
url = {https://claudskills.com/skills/plan-a-feature/}
}Embed this skill
Promote, attribute, or link this skill from your own README, blog post, or documentation. All three snippets are free to use — no sign-up, no API key. More distribution surfaces →
Badge
[](https://claudskills.com/skills/plan-a-feature/?utm_source=badge&utm_medium=readme&utm_campaign=skill_badge)
<script>
<script src="https://claudskills.com/embed/plan-a-feature.js" async></script>
<iframe>
<iframe src="https://claudskills.com/embed/plan-a-feature.html" width="100%" height="160" frameborder="0" loading="lazy" title="ClaudSkills: Plan A Feature"></iframe>
Security scan
Grade A · scanned 2026-10-25 — free static scan against the OWASP Agentic Skills Top 10.
The scan flagged 1 of 10 categories (filesystem), including lower-severity patterns. Patterns shown inside code fences are weighted as examples rather than instructions — read the grading methodology for what this does and does not guarantee.
- ✓ Prompt injection
- ✓ Data exfiltration
- ✓ Supply chain
- ✓ Reverse shell
- ✓ Credentials
- ✓ Execution
- ⚠ Filesystem
- ✓ Persistence
- ✓ Obfuscation
- ✓ Network
Show this grade on your repo (click to copy):
[](https://claudskills.com/skills/plan-a-feature/#security)
More Product skills
Browse all Product skills in the ClaudSkills registry, or explore these other picks from the same category:
Part of Acreator Store — Adam Lankamer's AI tools:
PerfectStudio ·
Ucaption ·
UTagger ·
AutoXPoster ·
TestYourSkills ·
AutomationFlows ·
Au Naturel ·
Telegram @acreatorstore