Skip to content
Back to skills

Retrospective

ASecurity

Run the CocoRetro periodic quality retrospective. Supports `$retrospective run` and `$retrospective status`.

  • 724 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 5, 2026
ai-agents

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add Snowflake-Labs/cocoplus --skill retrospective --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Retrospective?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Retrospective
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/snowflake-labs-retrospective/badge)](https://www.skillsdirectory.com/skills/snowflake-labs-retrospective)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "retrospective"
description: "Run the CocoRetro periodic quality retrospective. Supports `$retrospective run` and `$retrospective status`."
version: "2.0.0"
author: "CocoPlus"
tags:
  - cocoplus
  - retrospective
  - quality
---

Your objective is to run the periodic closed-loop quality retrospective.

## Commands

- `$retrospective status`: read `.cocoplus/lifecycle/retrospective-ledger.jsonl` and report last run, pending requests, and open actuator proposals.
- `$retrospective run`: analyze recent session artifacts, classify failure modes, propose the cheapest sufficient actuator, and append the result to the ledger.

## Failure Taxonomy

Use exactly one tag per attributable failure:

- `present-not-consulted`
- `present-contradicted`
- `absent-via-truncation`
- `absent-via-never-retrieved`
- `absent-via-compaction`
- `cant-tell`

## Actuator Hierarchy

Prefer the cheapest sufficient actuator:

1. hook or gate,
2. skill or command,
3. structural agent-level rule,
4. standing context.

Do not propose a standing-context addition unless the cheaper layers cannot enforce the rule.

## Exit Criteria

- [ ] Token-weighted wasted effort is reported.
- [ ] Every applied edit has a verbatim `after` anchor for future verification.
- [ ] The ledger records evidence, classification, proposed actuator, and decision.

## Anti-Rationalization

| Shortcut / Temptation | Why It Fails |
|-----------------------|--------------|
| Treat the skill as complete because the file exists | Skill contracts must describe observable behavior and verification, not just command names. |
| Skip artifact and safety checks for a small command | Small commands still mutate state or guide execution; preserve the same gates. |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…