From fcef7a9545798d3e3e8fc20433d5e7256a6340e9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gabor=20K=C3=B6rber?= Date: Thu, 17 Sep 2026 14:00:39 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=A4=96=20Add=20graduation=20candidates=20?= =?UTF-8?q?to=20Igor=20journal=20template?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- plugins/spire/skills/igor/SKILL.md | 2 +- plugins/spire/skills/igor/references/journal-template.md | 6 ++++++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/plugins/spire/skills/igor/SKILL.md b/plugins/spire/skills/igor/SKILL.md index b4bc43b..29410ed 100644 --- a/plugins/spire/skills/igor/SKILL.md +++ b/plugins/spire/skills/igor/SKILL.md @@ -120,5 +120,5 @@ Agent(subagent_type: "adept", name: "-adept", model: "opus", 1. **Setup** — journal, worktree if code will change. Skim the project's architecture entry point (`project.md` names it; otherwise the root CLAUDE.md/AGENTS.md) so you can catch misconceptions later. Then ask what the user wants. 2. **Work** — before touching a tool, classify: *is this work or conversation?* Reading code, running commands, producing an artifact: work, delegate it. Reasoning together, deciding direction, answering from context: conversation, stay present. When the user signals readiness ("let's do it," "go ahead," "make it happen"), formulate the brief from what was just discussed and dispatch. Don't ask whether to delegate; they already said so. Then: review results -> relay -> repeat. -3. **Wrap-up** — close the journal, state where everything landed. Then review the conversation for durable corrections to existing documents and accrete them now (dated section, link back to this journal). This is the minimum act that keeps the next session from re-deriving what this one understood. +3. **Wrap-up** — close the journal, state where everything landed. Then review the conversation for durable corrections to existing documents and accrete them now (dated section, link back to this journal). Finally, review the journal for entries that would earn a place in a knowledge base — insights where losing them would cost thinking work, not just a tool call. List them under `## Graduation candidates` with a one-line rationale each. This is the minimum act that keeps the next session from re-deriving what this one understood. 4. **Self-review** (user-triggered) — when the user asks to wrap up or clean up, record a brief self-review in the session journal before closing: where did you follow the mindset principles well, where did you deviate, what surprised you? This is accretion data for improving Igor — not a grade, just honest observation. Note specific moments ("I started reading code myself instead of delegating when the user said X", "the delegation default worked well here"). Keep it short — 3-5 bullet points. The user may also ask for this mid-session. diff --git a/plugins/spire/skills/igor/references/journal-template.md b/plugins/spire/skills/igor/references/journal-template.md index 94b1c4f..ceb4453 100644 --- a/plugins/spire/skills/igor/references/journal-template.md +++ b/plugins/spire/skills/igor/references/journal-template.md @@ -20,4 +20,10 @@ ## Open threads + +## Graduation candidates + + ```