Claude Skill

agent-environment-retrospective

Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download outlinedriven-outline-driven-development-.devin_skills_agent-environment-retrospective-b0e8ce8.zip · 1 KB

outlinedriven/outline-driven-development 54 10 forks Apache-2.0 Updated 2d ago

Part of outlinedriven/outline-driven-development — 145 skills

Install

skills CLI

npx skills add https://github.com/OutlineDriven/outline-driven-development/tree/main/.devin/skills/agent-environment-retrospective

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install outlinedriven-outline-driven-development@llmmart

Git git clone https://github.com/OutlineDriven/outline-driven-development.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole outlinedriven/outline-driven-development collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Agent-environment retrospective

Contract

Field	Bound contract
Trigger	A completed session needs an agent-environment retrospective.
Authority	Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation.
Side effect	Chat output: severity-ranked environment improvement candidates.
Done	Every candidate names evidence and the friction it removes.

Inputs

Session artifact (required): the completed session transcript or state record. Must contain observable agent-environment interaction.
Environment context (optional): the agent's working environment at session time. Use only if supplied; do not infer it.

Procedure

Gather inputs. Receive the session artifact and any supplied environment context. Done when: the session artifact is received and any supplied environment context is noted.
Identify friction. Scan the session artifact for patterns where the agent's environment created friction: tool failures, slow retries, missing context, state loss, repeated navigation, or unclear feedback. Done when: every friction pattern in the artifact is identified or the artifact is confirmed friction-free.
Classify candidates. Assign each friction point a type: tool-failure, slow-retry, missing-context, state-loss, navigation-overhead, or unclear-feedback. Done when: every identified friction point has an assigned type.
Rank by severity. Order candidates: high (blocks progress) → medium (degrades efficiency) → low (minor friction). When severity ties, prefer candidates with stronger evidence. Done when: candidates are ordered by severity with ties broken by evidence strength.
Validate evidence. For each candidate, confirm the named evidence appears in the session artifact. Candidates without traceable evidence are omitted. Done when: every candidate is either confirmed against traceable evidence, omitted, or retained as unconfirmed with its severity downgraded.
Return report. Output the severity-ranked candidate report. Done when: the report is emitted with every surviving candidate carrying type, evidence, severity, and friction_removed.

Failure and recovery

No session artifact: return an empty report stating "No session artifact supplied."
No friction observed: return a report stating "No environment friction detected." with zero candidates. Do not fabricate candidates.
Ambiguous evidence: downgrade the candidate to unconfirmed severity rather than guess. Include the ambiguity in the evidence field.

Output

A severity-ranked markdown report. Each candidate entry contains:

type: friction type
evidence: verbatim session evidence
severity: high, medium, or low
friction_removed: what eliminating this friction would achieve

Files (outline-driven-development)

agents

openai.yaml 155 B

interface:
  display_name: "Agent Environment Retrospective"
  short_description: "Use when a completed session needs an agent-environment retrospective."

SKILL.md 3 KB

---
name: agent-environment-retrospective
description: 'Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.'
---

# Agent-environment retrospective

## Contract

| Field | Bound contract |
|---|---|
| Trigger | A completed session needs an agent-environment retrospective. |
| Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. |
| Side effect | Chat output: severity-ranked environment improvement candidates. |
| Done | Every candidate names evidence and the friction it removes. |

## Inputs

- Session artifact (required): the completed session transcript or state record. Must contain observable agent-environment interaction.
- Environment context (optional): the agent's working environment at session time. Use only if supplied; do not infer it.

## Procedure

1. **Gather inputs.** Receive the session artifact and any supplied environment context. Done when: the session artifact is received and any supplied environment context is noted.
2. **Identify friction.** Scan the session artifact for patterns where the agent's environment created friction: tool failures, slow retries, missing context, state loss, repeated navigation, or unclear feedback. Done when: every friction pattern in the artifact is identified or the artifact is confirmed friction-free.
3. **Classify candidates.** Assign each friction point a type: `tool-failure`, `slow-retry`, `missing-context`, `state-loss`, `navigation-overhead`, or `unclear-feedback`. Done when: every identified friction point has an assigned type.
4. **Rank by severity.** Order candidates: high (blocks progress) → medium (degrades efficiency) → low (minor friction). When severity ties, prefer candidates with stronger evidence. Done when: candidates are ordered by severity with ties broken by evidence strength.
5. **Validate evidence.** For each candidate, confirm the named evidence appears in the session artifact. Candidates without traceable evidence are omitted. Done when: every candidate is either confirmed against traceable evidence, omitted, or retained as unconfirmed with its severity downgraded.
6. **Return report.** Output the severity-ranked candidate report. Done when: the report is emitted with every surviving candidate carrying type, evidence, severity, and friction_removed.

## Failure and recovery
- No session artifact: return an empty report stating "No session artifact supplied."
- No friction observed: return a report stating "No environment friction detected." with zero candidates. Do not fabricate candidates.
- Ambiguous evidence: downgrade the candidate to unconfirmed severity rather than guess. Include the ambiguity in the evidence field.

## Output
A severity-ranked markdown report. Each candidate entry contains:

- `type`: friction type
- `evidence`: verbatim session evidence
- `severity`: `high`, `medium`, or `low`
- `friction_removed`: what eliminating this friction would achieve