Verified:GitHub

extension-planner

Create Feature Requirement Documents and increment plans for new application features.

Updated Mar 30, 2026

Search Tags:#impact analysis #feature planning #brownfield development #feature requirement document #increment planning

Ready to run

npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill extension-planner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: extension-planner
Source: https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield/tree/main/.github/skills/extension-planner
Command: npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill extension-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in planning and documenting new feature additions to an existing application, streamlining the transition from user requirements to feature implementation.

Core Features & Use Cases

Feature Requirement Document Generation: Translates user requirements into detailed Feature Requirement Documents (FRDs).
Increment Planning: Defines a clear increment plan that aligns with the standard greenfield pipeline.
Impact Analysis: Conducts a thorough impact analysis on existing application components and data models.
Documentation: Provides guidelines for creating and updating necessary documentation.
Use Case: For a software developer planning to add a new notification feature to an existing app, this Skill will guide through creating the FRD and increment plan, ensuring all integration points are considered.

Quick Start

Use the extension-planner skill to begin the planning process for your new feature.

Frequently Asked Questions about extension-planner

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

FAQPage Schema

How do I plan new features for an existing application without breaking current functionality?▼

Feature planning for brownfield development requires assessing the impact on existing codebases and data models. Analyzing current architecture provides context to define requirements thoroughly and ensure a smooth transition to implementation.

What is the best way to document feature requirements for brownfield development?▼

Documenting feature requirements for brownfield development involves translating user needs into detailed Feature Requirement Documents (FRDs). This ensures integration points are considered and requirements are well-defined before implementation begins.

Can I generate an increment plan that aligns with greenfield pipelines for existing apps?▼

You can generate increment plans for existing applications that align with standard greenfield pipelines. This defines a clear, incremental transition path from user requirements to feature implementation.

How do I conduct an impact analysis on existing application components before adding a new feature?▼

Impact analysis on existing applications requires evaluating how new features affect current components and data models. Analyzing existing code and architecture ensures all integration points are assessed before implementation.

When do I need a Feature Requirement Document for adding to an existing codebase?▼

A Feature Requirement Document (FRD) is needed when adding new features to an existing codebase to ensure requirements are well-defined. It streamlines the transition from user requirements to implementation by providing thorough documentation.

Does this feature planning approach work for complex brownfield applications with existing data models?▼

Feature planning for brownfield applications works by utilizing analysis of existing code and architecture for context. It conducts thorough impact analysis on existing components and data models to ensure smooth implementation.