feedback-intake
Skill2 starsChanged 5 months agoMITView on GitHub
Processes formal performance feedback (project review, annual review, 360) into structured files and updates active development objectives. Keeps the career development loop closed.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- infragoodboys/claude-skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- infragoodboys/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- control-plane/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- control-plane/CLAUDE.mdCLAUDE.md
- agentic-os-reference-syncSkill
- branch-cleanupSkill
- capture-triageSkill
- darwin-housekeepingSkill
- darwin-path-modeSkill
- decision-log-entrySkill
- eodSkill
- expert-interview-guideSkill
- harness-onboardingSkill
- ingest-contentSkill
- meeting-to-work-itemsSkill
- memory-consolidateSkill
- morning-briefSkill
- os-bootstrap-extendSkill
- os-bootstrapSkill
- pr-reviewSkill
- scheduleSkill
- spec-cross-checkSkill
- ux-critiqueSkill
- weekly-retroSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
Never silently overwrite existing objectives — show what changed and why.
- Distinctive: line 44
Keep the feedback file confidential — don't surface its content in external outputs.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: feedback-intake
Purpose
Convert raw feedback into durable structure so it actually changes behavior — not just gets acknowledged and forgotten.
Steps
- Clarify the type (ask if unclear)
- Project / cycle feedback — granular, from a specific engagement or review cycle
- Annual / formal review — career-level synthesis, trajectory, forward plan
- Capture it
- Use
control-plane/memory/development/feedback/_template.md - Save to
control-plane/memory/development/feedback/YYYY-MM-DD-<slug>.md - Capture verbatim or close to verbatim — paraphrase only what is redundant. The original language matters.
- Mark anything uncertain as
(unconfirmed)
- Use
- Update
control-plane/memory/development/objectives.md- Project/cycle feedback: fold development areas into live objectives. Merge where the same underlying pattern. Keep max 3-4 live objectives. Add specific strengths to "Strengths to keep leveraging."
- Annual review: refresh objectives wholesale against the forward priorities. Retire mastered objectives with a note. Update the "Next review" date.
- Reflect back
- What changed in the objectives (be specific)
- ONE way to start practicing the newest or highest-priority objective tomorrow — tied to something real on the calendar or backlog
Rules
- Feedback is data, not a verdict. Frame adjustments accordingly.
- Never silently overwrite existing objectives — show what changed and why.
- The principal may want to push back on feedback. Create space for that before updating.
- Keep the feedback file confidential — don't surface its content in external outputs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.