# Rdd Defect Workflow

Trigger: RDD, receipt-driven development, review authority, receipt/lineage...

- Repository: https://github.com/Gentleman-Programming/gentle-ai (8170 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Gentleman-Programming/gentle-ai --skill rdd-defect-workflow -g -a claude-code -y`
Codex: `npx skills add Gentleman-Programming/gentle-ai --skill rdd-defect-workflow -g -a codex -y`
Cursor: `npx skills add Gentleman-Programming/gentle-ai --skill rdd-defect-workflow -g -a cursor -y`
Gemini CLI: `npx skills add Gentleman-Programming/gentle-ai --skill rdd-defect-workflow -g -a gemini-cli -y`

## Description

Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Activation Contract

Load when the frontmatter trigger terms apply to a defect workflow.

This skill guides public collaboration. It does not grant issue approval, label, review, exception, or merge authority.

## Hard Rules

- Check the user-owned RDD kill switch first. When disabled, do not start receipt reviews or fabricate approval; follow ordinary policy and report `disabled/unmanaged`.
- Require an approved issue (`status:approved`) and clean current `main` reproduction before implementation. Audit existing PRs for supersession or conflict; stop or narrow stale claims.
- Group by causal authority invariant. Use one issue and one PR or explicit chain per independent invariant and rollback boundary. Split independent causes; never merge a superseded or conflicting authority line.
- Inventory every operator flow claimed by the issue or PR, including entry, mode, environment, expectation, and negative controls. Require one truthful black-box bench journey per CLI or lifecycle flow, or actual runtime E2E proof when the core bench cannot represent it. Synthetic proxy coverage never proves another runtime.
- Use CodeGraph-first impact mapping, a dedicated worktree, and behavior-first tests. Run source-mutating normalization before candidate freeze.
- Forecast authored changes before edits. The hard limit is 400 additions plus deletions; above it, STOP for a chain or explicit maintainer-approved exception.
- Only when RDD is enabled, bind the review candidate identity, lineage, correction, and recovery records exactly. Keep bounded review defects in one correction transaction; ordinary repository policy decides delivery.
- Require independent read-only candidate validation before publication. Validation cannot edit source or authority; findings require a new candidate.
- Keep communication humane and evidence-based. Repository labels and workflow metadata are maintainer-owned, never evidence of contributor blame.

## Decision Gates

The rest: https://github.com/Gentleman-Programming/gentle-ai/blob/HEAD/internal/assets/skills/rdd-defect-workflow/SKILL.md