Skip to content

davepoon/buildwithclaude / plugins/all-skills/skills/feedback

feedback

Verified

Turn post-task feedback—even blunt or angry feedback—into an evidence-based, approval-gated improvement plan for the agent/user workflow. Use after agent work goes wrong, misses expectations, creates friction, or should improve in future. Never mutate during the feedback turn.

FileKindSize
LICENSEother1.0 KB
SKILL.mdskill md8.0 KB
references/approval-protocol.mdmarkdown1.4 KB
references/hosts/claude-code.mdmarkdown1.2 KB
references/hosts/codex.mdmarkdown1.2 KB
references/hosts/generic.mdmarkdown616 B
references/hosts/hermes.mdmarkdown1015 B
references/hosts/pi.mdmarkdown1.1 KB
references/privacy.mdmarkdown1.1 KB
references/routing.mdmarkdown2.3 KB

references/approval-protocol.md

View on GitHub
# Approval protocol

The feedback turn always ends in `AWAITING APPROVAL`.

## Required output

```markdown
# Feedback plan · <mission or artifact>

**Status:** AWAITING APPROVAL
**Host:** <verified host or Unknown>
**Evidence available:** <current context, artifact, session history, instructions, etc.>
**Evidence missing:** <material gaps or None>

## What happened
<Concise expected → observed → impact summary.>

## Diagnosis
**Primary class:** <class>
**Confidence:** high | medium | low

- **Observed:** ...
- **Inferred:** ...
- **Unknown:** ...

## Proposed improvements

### F1 · <short title>
- **Target:** <surface>
- **Action:** add | revise | remove | consolidate | no change
- **Problem addressed:** ...
- **Proposed change:** ...
- **Evidence:** ...
- **Expected benefit:** ...
- **Risk/trade-off:** ...
- **Verification:** ...

## Intentionally unchanged
- <Surface or behavior> — <why no change is warranted>.

## Collaboration contract
<Include only when useful. Otherwise say “No user-side change proposed.”>

## Approval
- `APPROVE ALL`
- `APPROVE F1,F3`
- `EDIT F2: <replacement scope>`
- `REJECT F4`

No changes have been applied.
```

Use 1–5 items by default. IDs stay stable once referenced. Every item needs verification. “Intentionally unchanged” is mandatory. A broad local approval never bundles publishing, deployment, sending, or deletion.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall