What problem does it solve? Adding functionality that was not in the original plan risks breaking completed work, contradicting accepted architecture decisions, and fragmenting requirements across files. This Skill integrates new features into an existing spec-driven project without silently breaking what is already built. ## Core Features & Use Cases - Impact Ripple Analysis: Scans architecture components, living behavior specs in docs/05-specs/_current/, and accepted ADRs to identify every component, business rule, and decision the new feature touches, including breaking changes. - Requirements Merge: Folds new user stories and business rules per-section into business_requirements.md with traceable markers, continuing existing ID numbering instead of appending addenda. - Roadmap and ADR Updates: Adds the feature as a new milestone or epic with explicit dependencies, supersedes conflicting ADRs, and hands off to the build phase. - Use Case: Mid-project, a stakeholder says "ahora también queremos notificaciones por email". The Skill maps which modules and specs ripple, flags a breaking schema change, gets explicit user approval via Plan mode, then updates the ROADMAP and routes to build. ## Quick Start Tell the agent you want to add a new feature not in the original roadmap, for example: "quiero agregar exportación de reportes a PDF al proyecto".
