feature-impact-analysis

Identify edge cases and cross-feature impacts from a feature spec.

Updated Feb 13, 2025
One-click install
npx skills add https://github.com/davehague/adulting.diy --skill feature-impact-analysis-davehague
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-impact-analysis
Source: https://github.com/davehague/adulting.diy/tree/main/.claude/skills/feature-impact-analysis
Command: npx skills add https://github.com/davehague/adulting.diy --skill feature-impact-analysis-davehague

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies edge cases and cross-feature impacts to prevent regressions when implementing a new feature.

Core Features & Use Cases

  • Systematically assess interactions between a new feature and existing functionality.
  • Document edge cases, data flows, permissions, and UX implications to guide implementation.
  • Use when a design spec exists and you want a thorough risk and requirement check before coding.

Quick Start

Review the feature design and run the impact analysis workflow to enumerate edge cases and affected areas.

Frequently Asked Questions about feature-impact-analysis

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

FAQPage Schema
How do I identify edge cases in a feature spec before coding?

To identify edge cases before coding, apply a structured impact analysis workflow that assesses interactions between the new feature and existing systems across UI, data, and permissions. This process enumerates potential regressions using a defined analysis framework.

What is the best way to assess cross-feature impacts for a new requirement?

Assessing cross-feature impacts involves applying an analysis framework to each existing feature interacting with the new requirement. This systematically documents data flows, permissions, and edge cases to guide implementation and prevent regressions.

How do I perform a design review to prevent feature regressions?

Perform a design review to prevent regressions by running an impact analysis workflow on your feature spec. This captures edge cases and affected areas by evaluating system interactions, data flows, and permissions in diverse scenarios.

Does feature impact analysis work without existing dependencies or components?

Feature impact analysis works without specific dependencies or components because it provides a self-contained workflow and canonical prompt template. You only need an existing feature design spec to begin assessing system interactions and risk.

When should I use a risk assessment workflow for feature analysis?

Use a risk assessment workflow for feature analysis when you have a design spec and need a thorough requirement check before coding. It is specifically designed to evaluate diverse scenarios and prevent regressions across UI, data, and permissions.