gd-start-impact-report

Analyze system architecture to generate impact reports covering frontend, backend, database, and integrations.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/carlosamesar/framework-sdd --skill gd-start-impact-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gd-start-impact-report
Source: https://github.com/carlosamesar/framework-sdd/tree/main/.opencode/skills/gd-start-impact-report
Command: npx skills add https://github.com/carlosamesar/framework-sdd --skill gd-start-impact-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a mandatory technical impact report before starting implementation, reducing risks associated with changes in legacy and integrated systems.

Core Features & Use Cases

  • Impact Assessment: Generates structured reports detailing frontend, backend, database, and integration effects.
  • Risk Identification: Produces a risk map highlighting high and medium risk areas, dependencies, and potential issues.
  • Decision Support: Assists teams in making informed go/no-go decisions based on comprehensive impact analysis.
  • Use Case: When planning a feature update involving multiple layers, use this Skill to identify surfaces of impact and prevent regression or compatibility issues.

Quick Start

Trigger this skill during /gd:start to build an impact report including affected files, modules, and potential risks.

Frequently Asked Questions about gd-start-impact-report

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

FAQPage Schema
How do I generate a technical impact report for system architecture changes?▼

To generate an impact report, analyze system architecture to document affected frontend, backend, database, and integration components, producing a structured risk assessment that minimizes deployment risks.

What is technical impact analysis in software engineering?▼

Technical impact analysis is the process of evaluating system architecture to identify dependencies, map integration effects, and highlight high-risk areas before code implementation to prevent regression and compatibility issues.

How do I assess deployment safety for legacy system updates?▼

Assess deployment safety by mapping integration points and validating all affected components against safety gates, ensuring comprehensive documentation of medium and high-risk areas before making go/no-go decisions.

Can I use impact analysis for multi-layer feature updates?▼

Yes, you can use impact analysis for multi-layer feature updates to identify surfaces of impact across frontend, backend, and database layers, preventing regression or compatibility issues before deployment.

How do I identify high risk areas before code deployment?▼

Identify high-risk areas before code deployment by mapping system dependencies and validating potential issues against safety gates, generating a risk map that highlights vulnerabilities across affected modules.