receipt-stream

Generate per-cycle cdd-iteration artifacts and update INDEX.md during cycle close-out.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill receipt-stream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receipt-stream
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.handoff/skills/handoff/receipt-stream
Command: npx skills add https://github.com/usurobor/cnos --skill receipt-stream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures a durable, auditable learning signal for the protocol by producing per-cycle iteration artifacts (cdd-iteration.md) and updating a persistent cross-cycle index (INDEX.md) so ε can surface patterns across cycles.

Core Features & Use Cases

  • Per-cycle artifact generation: writes a structured cdd-iteration.md with the canonical finding shape for γ-closeouts and ε reviews.
  • Cross-cycle aggregation: appends a row to .cdd/iterations/INDEX.md after each cycle that produces an iteration artifact.
  • Lifecycle tracing: guarantees alignment between cycle close-outs, artifacts, and their cross-repo traces, preserving auditability and learning signals.

Quick Start

Create the per-cycle cdd-iteration.md during cycle close-out and update INDEX.md accordingly.

Frequently Asked Questions about receipt-stream

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

FAQPage Schema
How do I maintain cross-cycle protocol learning artifacts across handoff stages?

Protocol learning artifacts are maintained by generating per-cycle cdd-iteration.md files during close-out and appending entries to a central INDEX.md, preserving auditability across handoff, cdd, and epsilon roles.

What is the canonical INDEX.md format for aggregating cross-cycle iteration artifacts?

The canonical INDEX.md format for cross-cycle aggregation uses an eight-column structure that records each cycle artifact, enforcing cross-repo bundle and archival invariants to surface patterns across iterations.

How do I handle cycle close-out when protocol_gap_count is greater than zero?

Cycle close-out with protocol_gap_count greater than zero is handled by enforcing the canonical per-finding shape inside cdd-iteration.md, while optionally writing courtesy stubs for clean cycles to maintain learning signals.

When do I need to generate per-cycle iteration artifacts for protocol reviews?

Per-cycle iteration artifacts are needed during gamma-closeouts and epsilon reviews to guarantee alignment between cycle close-outs, artifacts, and their cross-repo traces, ensuring a durable and auditable learning signal.

Does cycle close-out enforce cross-repo bundle and archival invariants?

Cycle close-out enforces cross-repo bundle and archival invariants by producing per-cycle cdd-iteration artifacts and updating the persistent cross-cycle index, ensuring traces remain aligned and auditable across repositories.

What's the best way to automate cross-cycle learning signal updates after a protocol cycle?

Cross-cycle learning signal updates are automated by writing structured cdd-iteration.md files during cycle close-out and appending rows to .cdd/iterations/INDEX.md, enforcing the canonical eight-column format automatically.