requirement-comparison-reporter

Compare requirement document versions and generate Markdown modification plans.

142|14|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill requirement-comparison-reporter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirement-comparison-reporter
Source: https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/requirement-comparison-reporter
Command: npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill requirement-comparison-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill bridges the gap between evolving requirement documents and the software code that implements them, ensuring that changes are accurately tracked, their impact is understood, and a clear plan for modification is generated.

Core Features & Use Cases

  • Requirement Change Analysis: Identifies added, modified, and removed requirements between document versions.
  • Code Impact Assessment: Maps requirement changes to specific code components (files, classes, functions).
  • Modification Planning: Generates a detailed plan outlining components to modify, delete, or add, along with test impact and dependency analysis.
  • Use Case: After a new feature is requested, use this Skill to compare the updated requirements against the existing codebase, identify all affected files and functions, and produce a clear list of code changes needed, including new files to create and old ones to remove.

Quick Start

Use the requirement-comparison-reporter skill to compare the files 'old_requirements.md' and 'new_requirements.md' and analyze their impact on the code in the '/path/to/your/repo' directory.

Frequently Asked Questions about requirement-comparison-reporter

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

FAQPage Schema
How do I analyze code impact from requirement changes in a repository?

Code impact analysis maps requirement changes to specific code components by comparing old and new requirement documents, identifying exactly which files, classes, and functions require modification, deletion, or addition.

What is requirement traceability and how does it work with code modification planning?

Requirement traceability links evolving requirement documents directly to software code, ensuring changes are accurately tracked and mapped to a comprehensive modification plan outlining components to modify, delete, or add.

How do I generate a modification plan from updated Markdown requirement documents?

You generate a modification plan by comparing text or Markdown requirement versions to identify functional and API changes, then producing a detailed Markdown report covering dependency analysis, integration points, and test impact.

Can I compare requirement versions to find deleted features and API changes?

Yes, comparing requirement versions identifies added, modified, and removed requirements, specifically detecting feature-level, functional, and API changes to determine which code components must be deleted or updated.

Does requirement comparison support analyzing test impact and dependencies?

Yes, requirement comparison assesses test impact and analyzes dependencies by evaluating integration points within the code repository, incorporating these findings directly into the generated modification plan.