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

cr-generate

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

3|Updated May 28, 2026
Search Tags:#routing#traceability#sdlc#approval#cr#work-package#change-request
One-click install
npx skills add https://github.com/mahg-es/araya --skill cr-generate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cr-generate
Source: https://github.com/mahg-es/araya/tree/main/skills/cr-generate
Command: npx skills add https://github.com/mahg-es/araya --skill cr-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert approved DRR findings into formal Change Requests that become new work packages. Each CR routes back into the proper SDLC lifecycle.

Core Features & Use Cases

  • Create CR records for approved findings and link them to the original DRR and IAR.
  • Route CRs by finding type (Missing Requirement, Bug, UX/UI, Security, Performance, Documentation) to appropriate lifecycle steps.
  • Maintain CR status (approved, rejected, deferred, needs_clarification) and store in the repository at .araya/reviews/cr/.

Quick Start

After Manu approves findings, run the CR generation workflow to emit a YAML CR file for each approved finding into .araya/reviews/cr/.

Frequently Asked Questions about cr-generate

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

FAQPage Schema
How do I convert approved findings into formal change requests for SDLC routing?▼

To convert approved findings into change requests, the cr-generate Skill creates formal CR records linked to original DRR and IAR documents, routing each finding to appropriate lifecycle steps. It outputs YAML files to the .araya/reviews/cr/ directory.

What finding types can be routed as change requests into work packages?▼

Change request routing supports finding types including Missing Requirement, Bug, UX/UI, Security, Performance, and Documentation. Each type routes to its appropriate SDLC lifecycle step to become a new work package.

How does change request status handling work for deferred or rejected findings?▼

Change request status handling maintains records as approved, rejected, deferred, or needs_clarification. These statuses are persisted in YAML format within the .araya/reviews/cr/ repository path for traceability.

Do I need IAR completion and approval decisions before generating change requests?▼

Yes, IAR completion and Manu's approval decisions are required prerequisites. The change request generation workflow processes only approved DRR findings to ensure traceability before creating new work packages.

What is the best way to persist change requests for repository traceability?▼

The best way to persist change requests for traceability is storing them as YAML files in the .araya/reviews/cr/ directory. This format maintains CR status and links findings back to original DRR and IAR records.

Why does cr-generate route findings by type instead of creating generic work packages?▼

Routing findings by type ensures each change request enters the correct SDLC lifecycle path. This per-type routing mechanism maintains traceability from DRR findings through to formal work packages instead of generating generic tasks.

Related Skills

Explore More Product & Management Skills→
mahg-esmahg-es
3

iar-generate

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

Official
Intermediate
FrkAkFrkAk
178

manage

Manage a project's context network and propagate task changes through downstream dependencies.

Community
Advanced
joshbandjoshband
3

impl

Execute LocusQ DSP and WebView implementation tasks with ADR-compliant traceability.

Community
Advanced
volodchenkovvolodchenkov
2

plane-operations

Automate Plane issue creation, sub-issue handling, comments, and artifact status updates.

Community
Advanced