Menu
Generate Change Requests (CR) from approved findings, creating new work packages that route back into the SDLC.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | cr-generate |
| description | Generate Change Requests (CR) from approved findings, creating new work packages that route back into the SDLC. |
Convert approved DRR findings into formal Change Requests that become new work packages. Each CR routes back into the proper SDLC lifecycle.
Approved findings without CRs are forgotten. CRs transform feedback into actionable work packages with traceability to the original delivery.
After IAR is complete and Manu (PO) has approved which findings to address.
DRR ID, IAR ID, and Manu's approval decisions.
.araya/reviews/cr/{cr_id}.yamlcr_id: CR-2026-014
source_drr: DRR-2026-001
source_iar: IAR-2026-001
status: approved
findings:
- finding_id: DRR-001
route: SDD → BDD → TDD → Implementation
work_package: WP-2026-007
impact:
sdd: true
bdd: true
tdd: true
architecture: false
Structured CR saved to .araya/reviews/cr/. Sonia uses CR to create
the next work package and route it back into /araya run.
.araya/reviews/cr/Consult and write the ARAYA postoffice — the operational-directive channel. Advisory, never a gate: read it at cycle start, append your entry at cycle end, consider its directives, never be blocked by it. Governance acts never travel the postoffice.
Audit and enforce brand compliance across all projects and platforms — logo,
Design REST and GraphQL APIs following OpenAPI 3.1 standards. Produce complete
Connect frontend to backend — type-safe API clients, request/response handling,
Implement authentication and authorization middleware — JWT validation, role-based
Design scalable component architectures — design systems, component libraries,