agent-environment-retrospective
SolidUse when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.
AI & Automation 52 stars
9 forks Updated 5 days ago Apache-2.0
Install
Quality Score: 83/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# 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 progre...
Details
- Author
- OutlineDriven
- Repository
- OutlineDriven/outline-driven-development
- Created
- 9 months ago
- Last Updated
- 5 days ago
- Language
- Python
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Listed
agent-environment-retrospective
Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.
35 Updated 5 days ago
OutlineDriven AI & Automation Listed
retro
Conduct a retrospective on a coding session.
1 Updated 3 days ago
RSickenberg AI & Automation Listed
retrospect
Session retrospect — analyze the current Claude Code session against the rules it ran under (project and global `CLAUDE.md`), identify friction patterns and root causes, propose context-appropriate improvement actions, then execute after user approval.
1 Updated yesterday
devseunggwan