agentleFS
qkitzeroqkitzero/kage-bunshin/.claude/skills/learning/SKILL.md

learning

Skill1 starsChanged 8 months agoMITView on GitHub

Structured retrospective and lesson extraction. Use when reflecting on completed work or projects. Triggered by "learning", "retrospective", "what did we learn?", "reflection", or "what to apply next time".

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use open questions to help the user elaborate on details.

    line 24
  2. Very specific:

    If NOTEBOOK_PATH is set, search for past lessons related to the retrospective target:

    line 28
  3. Distinctive:

    Read up to 3 matching entries (frontmatter + first 200 characters of body)

    line 31
  4. Very specific:

    Create a team with the following teammates using their agent definitions from .claude/agents/:

    line 38

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Learning Skill

A workflow that creates an Agent Team of Researcher and Analyst to perform structured retrospectives through evidence-based analysis and discussion.

Workflow

Step 1: Understand the Retrospective Target

Accurately understand the retrospective target presented by the user. Clarify:

  • Subject (project, sprint, decision, event, etc.)
  • Time period (from when to when)
  • Stakeholders & context
  • Original goals & expectations

Use open questions to help the user elaborate on details.

Step 2: Retrieve Past Notebook Context

If NOTEBOOK_PATH is set, search for past lessons related to the retrospective target:

  1. Grep $NOTEBOOK_PATH/learnings/ and $NOTEBOOK_PATH/research/ for keywords from the target (searching title, tags, and body)
  2. Read up to 3 matching entries (frontmatter + first 200 characters of body)
  3. Include the retrieved content as context when creating the team

Skip this step if zero matches or NOTEBOOK_PATH is not set.

Step 3: Create Agent Team

Create a team with the following teammates using their agent definitions from .claude/agents/:

Teammates:

  • researcher — gathers evidence, data, and context about what happened
  • analyst — performs structured retrospective analysis

Team instructions:

Retrospective target: [Subject]
Time period: [Period]
Original goals: [Goals and expectations]
[Past Notebook context if found]

Collaboration protocol:
1. Researcher gathers evidence: project history, outcomes, metrics, related context from Notebook and codebase
2. Analyst performs initial retrospective analysis (what went well, what didn't, patterns, key learnings)
3. Researcher challenges the analysis — verifies claims against evidence, surfaces overlooked factors
4. Analyst refines the analysis based on Researcher's input, deepens root cause analysis
5. Continue iterating until both agree the lessons are well-evidenced and actionable (aim for 2-3 rounds)

Rules:
- Output language: Use the language specified by OUTPUT_LANGUAGE env var. If not set, match the user's language (default: English)
- If NOTEBOOK_PATH is set: Researcher saves evidence summary to $NOTEBOOK_PATH/research/, Analyst saves retrospective to $NOTEBOOK_PATH/learnings/
- Each agent writes its own deliverables with structured frontmatter (Analyst must use type: learning)

Step 4: Final Output

## Retrospective: [Subject]

### Discussion Summary
[How the retrospective analysis evolved through team discussion]

### Time Period & Context
[Overview]

---

### What Went Well
1. **[Item]**: [Description]
   - Evidence: [Supporting data from Researcher]
2. ...

### What Didn't Go Well
1. **[Item]**: [Description]
   - Root cause: ...
   - Evidence: [Supporting data from Researcher]
2. ...

### Patterns
- [Recurring trends observed, validated by evidence]

### What to Do Differently
| Action | Priority | Notes |
|--------|----------|-------|
| ... | High | ... |

### Key Learnings
1. **[Lesson Title]**: [Generalized learning]
2. ...
3. ...

---

### Notebook Save
- [Save status and location]

Output Format

Present the following to the user:

  1. Brief summary of the team discussion process
  2. What went well / What didn't go well (with evidence)
  3. Discovered patterns
  4. Specific improvement actions (with priority)
  5. Key lessons (3)
  6. Notebook save status

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.