skills.rest
fernando-fernandez3
fernando-fernandez3COMMUNITY
Explore all skills by this author →
GitHub

feature

Guide product teams through feature planning from requirements to governance.

Updated Aug 27, 2026
Search Tags:#requirements#roadmap#architecture design#approval gates#feature-planning#planning workflow
One-click install
npx skills add https://github.com/fernando-fernandez3/claude-code-resources --skill feature-fernando-fernandez3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/fernando-fernandez3/claude-code-resources/tree/main/my-config/skills/feature
Command: npx skills add https://github.com/fernando-fernandez3/claude-code-resources --skill feature-fernando-fernandez3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides product teams through exhaustive feature planning from requirements to governance.

Core Features & Use Cases

  • Exhaustive requirements gathering and architecture design for new features.
  • Clear approval-gate workflows to prevent premature implementation.
  • Structured plans and artifacts that align teams and stakeholders.

Quick Start

Use the feature skill to plan a new capability: /feature "Add a new reporting module with role-based access and audit trails".

Frequently Asked Questions about feature

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

FAQPage Schema
What artifacts do I need for architecture design and requirements gathering?▼

Architecture design and requirements gathering require specific artifacts including a Requirements Document, Architecture Design, and Implementation Plan. These documents align stakeholders and support iterative clarifications throughout the workflow.

How do I structure feature planning to get fast stakeholder approvals?▼

Feature planning requires structured artifacts like Requirements Documents and Architecture Designs to align teams and enforce approval gates before implementation. This prevents premature development and drives faster governance sign-off.

What is the best way to plan a major software enhancement without missing requirements?▼

Exhaustive feature planning for major enhancements uses iterative clarifications to capture all requirements before architecture design. This structured workflow ensures no details are missed and produces a clear implementation plan.

Can I use this feature planning workflow for complex system refactors?▼

Yes, feature planning workflows apply to complex refactors by guiding teams through requirements gathering and architecture design. The structured path provides governance and approval gates specifically for complex system changes.

How do I prevent premature implementation during the product planning workflow?▼

Preventing premature implementation requires clear approval-gate workflows within your planning process. By enforcing artifacts like an Implementation Plan and Requirements Document, teams must achieve governance sign-off before coding begins.

What artifacts do I need for architecture design and requirements gathering?▼

Architecture design and requirements gathering require specific artifacts including a Requirements Document, Architecture Design, and Implementation Plan. These documents align stakeholders and support iterative clarifications throughout the workflow.

Related Skills

Explore More Product & Management Skills→
microsoftmicrosoft
123

eval-guide

Define agent purpose, success criteria, and evaluation scope into test artifacts.

Official
Advanced
andrewvaughanandrewvaughan
12

build-feature

Automates full-stack feature implementation from an approved plan across database, API, frontend, and tests.

Community
Advanced
rysweetrysweet
1

roadmap-strategist

Plan and optimize project roadmaps, goals, milestones, and strategic direction.

Community
Basic
jongensutrechtjongensutrecht
1

plan-to-bmad

Convert plans, issues, and review notes into BMAD-ready Markdown and JSON.

Community
Advanced