agw-deep-feature-analysis

Document domain context, scope, and terminology for feature analysis requests.

2|1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/cucurb-it/analysis-gated-workflow-skills --skill agw-deep-feature-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agw-deep-feature-analysis
Source: https://github.com/cucurb-it/analysis-gated-workflow-skills/tree/main/skills/01-deep-feature-analysis
Command: npx skills add https://github.com/cucurb-it/analysis-gated-workflow-skills --skill agw-deep-feature-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents implementation errors by forcing a rigorous, phase-gated analysis of feature requests before any code is touched, ensuring total alignment between the Architect and the AI.

Core Features & Use Cases

  • Structured Analysis: Captures domain context, scope boundaries, and key terminology in a standardized format.
  • Ambiguity Resolution: Identifies open questions and gaps in requirements before development begins.
  • Use Case: When a stakeholder requests a complex refactoring, use this Skill to document the business capability and technical scope, ensuring the AI understands the requirements perfectly before proposing a solution.

Quick Start

Use the agw-deep-feature-analysis skill to begin the analysis phase for the new user authentication module.

Frequently Asked Questions about agw-deep-feature-analysis

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

FAQPage Schema
How do I document deep feature analysis for complex software refactoring requests?

Deep feature analysis is documented by capturing domain context, scope boundaries, and key terminology in a standardized format. This structured documentation ensures total alignment between the Architect and AI before proposing a solution.

When do I need a gated process for feature specification before coding?

A gated process for feature specification is needed when a stakeholder requests complex refactoring. It forces rigorous analysis to resolve requirement ambiguities and identify scope gaps, preventing implementation errors before any code is touched.

How do I resolve requirement ambiguities for a new software development module?

Resolve requirement ambiguities by structuring the feature analysis to explicitly identify open questions and gaps in requirements. This phase-gated progression requires explicit Architect-led validation before development begins.

Can I use this feature analysis workflow without accessing the codebase?

Yes, this feature analysis workflow operates within the Analysis-Gated Workflow without accessing the codebase. It captures business capabilities and technical scope independently to ensure requirements are understood perfectly.

What is the best way to structure complex features before coding begins?

The best way to structure complex features is using a phase-gated analysis that documents domain context, scope, and terminology. This approach satisfies the requirement for explicit Architect-led validation prior to implementation.

Why does complex refactoring require explicit Architect-led validation?

Complex refactoring requires explicit Architect-led validation to ensure total alignment between the Architect and the AI. This gated progression prevents implementation errors by validating the documented feature scope before coding.