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

drr-create

Create DRR findings with categories and severities, saved as YAML under .araya/reviews/drr/.

3|Updated May 28, 2026
Search Tags:#yaml#governance#traceability#findings#drr#post-delivery#delivery-review-report
One-click install
npx skills add https://github.com/mahg-es/araya --skill drr-create
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: drr-create
Source: https://github.com/mahg-es/araya/tree/main/skills/drr-create
Command: npx skills add https://github.com/mahg-es/araya --skill drr-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-delivery feedback is lost in chat history, comments, and ad-hoc discussions. DRRs formalize every observation as a traceable finding with category, severity, reviewer, and status.

Core Features & Use Cases

  • Create a DRR with a unique ID and record delivery feedback as structured findings with categories and severities.
  • Save the DRR to the repository path .araya/reviews/drr/ and track status over time.
  • Use cases include post-delivery reviews, stakeholder feedback, and PO sign-off documentation.

Quick Start

Create the DRR with a unique ID and save it to .araya/reviews/drr/.

Frequently Asked Questions about drr-create

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

FAQPage Schema
How do I formalize post-delivery feedback into traceable findings?▼

To capture post-delivery feedback as traceable findings, you create a Delivery Review Report. This formalizes observations from product reviews by assigning categories and severities to each finding for structured tracking.

What is a Delivery Review Report and when do I need it?▼

A Delivery Review Report (DRR) is a formal record used after product deliveries are reviewed by stakeholders. You need it to capture observations, categorize findings, and assign severities, preventing feedback from being lost in ad-hoc discussions.

How do I save a DRR as YAML for delivery governance?▼

You can save a DRR as YAML for delivery governance by persisting it under the .araya/reviews/drr/ repository path. The file structure includes fields like drr_id, delivery_id, reviewer, and findings to maintain traceability.

Can I use a DRR to document stakeholder feedback and PO sign-off?▼

Yes, you can use a DRR to document stakeholder feedback and PO sign-off. It captures post-delivery reviews by recording the reviewer for each formal finding and tracking the status over time.

What's the best way to track delivery review status over time?▼

The best way to track delivery review status over time is by persisting findings as a YAML file in the .araya/reviews/drr/ directory. This ensures every observation remains a traceable finding with category, severity, reviewer, and status fields.

Related Skills

Explore More Product & Management Skills→
MSiccDevMSiccDev
20

arc42-section-01

Guide arc42 Section 1 documentation by capturing system purpose, quality goals, and stakeholders.

Official
Intermediate
mahg-esmahg-es
3

iar-generate

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

Official
Intermediate
etylsarinetylsarin
59

git-workflow

Enforce feature-branch pull request workflows and prevent direct commits to main.

Community
Intermediate
MichaelSolatiMichaelSolati

playtesting

Generates a structured report from your raw, scattered game test notes.

Community
Advanced