skills.rest
VIPER-Metrics
VIPER-MetricsOFFICIAL
Explore all skills by this author →
GitHub

feature-planner

Plan GitHub feature requests into implementation plans with architecture and testing steps.

1|Updated Jan 19, 2026
Search Tags:#planning#architecture#GitHub#feature#issue#wiki
One-click install
npx skills add https://github.com/VIPER-Metrics/claude-code-skills --skill feature-planner-viper-metrics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-planner
Source: https://github.com/VIPER-Metrics/claude-code-skills/tree/main/skills/feature-planner
Command: npx skills add https://github.com/VIPER-Metrics/claude-code-skills --skill feature-planner-viper-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps teams transform a GitHub feature request issue into a structured, actionable implementation plan, enabling faster planning and alignment across stakeholders.

Core Features & Use Cases

  • Extract requirements from the issue and identify user stories, acceptance criteria, and use cases.
  • Generate a step-by-step implementation plan, including architecture or module breakdown, risk assessment, and testing strategy.
  • Save the plan to wiki/issues/{issue_number}/feature-plan.md and attach it back to the GitHub issue for visibility.

Quick Start

Use the feature-planner with a GitHub issue number to generate a plan: /feature-planner {issue_number}

Frequently Asked Questions about feature-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a GitHub feature request issue into an actionable implementation plan?▼

Turn a GitHub feature request into an actionable implementation plan by extracting requirements, defining architecture, assessing risks, and sequencing tasks. The plan is saved to wiki/issues/{issue_number}/feature-plan.md and attached back to the issue.

What is the best way to plan feature architecture and task sequencing from a GitHub issue?▼

The best way to plan feature architecture from a GitHub issue is to extract requirements, evaluate architecture decisions, and sequence implementation tasks. This yields a detailed plan with an architecture overview, data model considerations, and testing strategies.

Can I generate a testing strategy and requirements analysis directly from a GitHub enhancement issue?▼

Yes, you can generate a testing strategy and requirements analysis directly from a GitHub enhancement issue. The process extracts user stories, acceptance criteria, and use cases, then formulates a comprehensive testing strategy for the feature.

Does the feature planning process save the implementation plan back to the GitHub issue?▼

Yes, the feature planning process saves the implementation plan to wiki/issues/{issue_number}/feature-plan.md and attaches it back to the GitHub issue, ensuring visibility and alignment across all stakeholders.

What do I need to start planning a feature from a GitHub issue?▼

To start planning a feature from a GitHub issue, you need a feature or enhancement issue across your repositories and its issue number. The planner guides you through requirements extraction, architecture decisions, and risk assessment to ready the feature for development.

Related Skills

Explore More Product & Management Skills→
ruskibeatsruskibeats

triage

Classify GitHub issues as bugs or enhancements and manage state transitions.

Community
Advanced
TheBushidoCollectiveTheBushidoCollective
187

git-storytelling-commit-strategy

Plans commit strategies for software development workflows with atomic commits and a four-stage story arc.

Official
Basic
PiklarPiklar

speckit-taskstoissues

Convert project tasks into dependency-ordered GitHub issues.

Community
Advanced
royhenengelroyhenengel

plan

Generate spec-driven implementation plans for software development tasks.

Community
Intermediate