skills.rest
ZTE-AICloud
ZTE-AICloudOFFICIAL
Explore all skills by this author →
GitHub

spec-impact-analyze

Analyze requirements and specs to produce structured context for FEATURE_DIR/context.md.

52|3|Updated Feb 14, 2026
Search Tags:#architecture#context#requirements#spec#traceability#impact-analysis
One-click install
npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill spec-impact-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-impact-analyze
Source: https://github.com/ZTE-AICloud/Co-OmniSpec/tree/main/skills/spec-impact-analyze
Command: npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill spec-impact-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill automates impact analysis starting from user requirements by pulling and organizing knowledge from DOC_DIR/specs, identifying reusable scope and ripple effects, and producing a structured contextual intermediate for FEATURE_DIR/context.md without writing files directly.

Core Features & Use Cases

  • Extracts goals, stakeholders, business value, and key concepts from requirements and existing specs.
  • Maps REQ/SCN/FUNC/API/ENTITY and relationships in the relations folder to surface traceable context for downstream use.
  • Reuses and augments prior analyses to provide architecture terminology, mappings, constraints, and assumptions to guide later steps.
  • Outputs a structured intermediate context that can be consumed by upper-layer commands to populate FEATURE_DIR/context.md.

Quick Start

From the provided requirements and specs, generate a structured context ready to be inserted into FEATURE_DIR/context.md.

Frequently Asked Questions about spec-impact-analyze

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

FAQPage Schema
How do I perform impact analysis from requirements on existing specs?▼

Impact analysis from requirements is performed by extracting goals and stakeholders, mapping REQ/SCN/FUNC/API/ENTITY relationships from DOC_DIR/specs, and producing a structured intermediate context for FEATURE_DIR/context.md.

What is requirements traceability and how does it map to architecture context?▼

Requirements traceability maps relationships between requirements, scenarios, functions, APIs, and entities to surface architecture terminology, constraints, and cross-impact context for downstream development steps.

How do I identify reusable scope and ripple effects before writing feature specifications?▼

To identify reusable scope and ripple effects, analyze requirements against existing specifications in DOC_DIR/specs to extract cross-impact context and highlight available reuse opportunities for your feature.

Do I need to manually update context.md after generating impact context?▼

No, you do not need to manually update context.md during analysis. The process outputs a structured intermediate context that upper-layer commands feed into FEATURE_DIR/context.md without writing files directly.

Can I use this approach to extract stakeholders and business value from raw requirements?▼

Yes, you can extract stakeholders, business value, goals, and key concepts from raw requirements by cross-referencing them with existing specifications and applying relations JSON to surface structured context.

Related Skills

Explore More Software Engineering Skills→
ZTE-AICloudZTE-AICloud
52

archive

Parse change directives and propagate them into documentation specification suites.

Official
Advanced
StrategicMilkStrategicMilk

Requirement Specification

Generate Given-When-Then acceptance criteria from ambiguous user requests.

Community
Intermediate
duggal1duggal1
2

extract

Extract reusable UI components and design tokens into a unified design system.

Community
Advanced
quangphu1912quangphu1912
1

tracing-dependencies

Detects circular dependencies, architectural violations, and conflicts in module graphs via static code analysis.

Community
Advanced