skills.rest
mahg-es
mahg-esOFFICIAL
Explore all skills by this author →
WebsiteGitHub

iar-generate

Map DRR findings to affected project artifacts and estimate effort and risk.

3|Updated May 28, 2026
Search Tags:#traceability#risk-assessment#software-engineering#change-management#impact-analysis#artifact-mapping#iar
One-click install
npx skills add https://github.com/mahg-es/araya --skill iar-generate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iar-generate
Source: https://github.com/mahg-es/araya/tree/main/skills/iar-generate
Command: npx skills add https://github.com/mahg-es/araya --skill iar-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This analysis identifies which project artifacts are affected by DRR findings, enabling targeted remediation and efficient planning.

Core Features & Use Cases

  • Artifact mapping: links each DRR finding to affected artifacts (SDD, BDD, TDD, architecture, implementation, UI, and documentation).
  • Effort estimation: assigns effort (story points) per finding to support planning.
  • Risk assessment: categorizes findings by risk level to guide prioritization.
  • Use Case: after a DRR is created, generate an IAR to drive changes and traceability.

Quick Start

Provide the DRR and project context; the skill will generate a complete IAR YAML report and store it under .araya/reviews/iar/.

Frequently Asked Questions about iar-generate

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

FAQPage Schema
How do I map design review findings to affected software artifacts for impact analysis?▼

To map design review findings to affected software artifacts for impact analysis, provide the DRR and project context to generate an IAR. This links each finding to affected artifacts like SDD, BDD, TDD, architecture, implementation, UI, and documentation.

What is artifact mapping in change management and when do I need it?▼

Artifact mapping in change management links review findings to specific project artifacts to enable targeted remediation. You need it after a DRR is created to drive changes, establish traceability, and efficiently plan fixes across your software engineering project.

How do I estimate remediation effort and assess risk for design review findings?▼

To estimate remediation effort and assess risk for design review findings, apply the DRR within the full project context. This assigns effort in story points per finding and categorizes risk levels to guide prioritization and planning.

Can I generate a traceability report in YAML format for my design review findings?▼

Yes, you can generate a traceability report in YAML format for design review findings. The process persists a complete IAR YAML report containing artifact mappings, effort estimates, and risk assessments to the .araya/reviews/iar/ directory.

Does impact analysis for software engineering require external dependencies to run?▼

No, impact analysis for software engineering does not require external dependencies to run. You only need to provide the DRR and the project context to map affected artifacts, estimate effort, and assess risk per finding without additional setup.

Related Skills

Explore More Software Engineering Skills→
venikmanvenikman

design/record-drr

Create ADR-style Design-Rationale Records with sequential prefixes in Markdown.

Community
Basic
mahg-esmahg-es
3

cr-generate

Convert approved DRR findings into YAML Change Requests stored in .araya/reviews/cr/.

Official
Intermediate
rlagycksrlagycks
3

project-guidelines-example

Document project architecture, workflows, code patterns, and testing procedures.

Community
Basic
bs-koobs-koo

impact-analysis

Trace ID chains to identify impacted artifacts and estimate change effort.

Community
Advanced