Skill

post-session-reflection

Use at the end of a cryptozavr research session (or when the user asks "wrap up" / "what did we do"). Produces a disciplined 3-bullet summary — artifacts produced, decisions made, what's next — so the next session starts warm.

npx claudepluginhub evgenygurin/cryptozavr --plugin cryptozavr

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/cryptozavr:post-session-reflection

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Use this skill when the user signals the session is winding down (phrases

SKILL.md

46 lines · ~521 tokens

Similar Skills

receiving-code-review

212.3k

Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.

superpowers

Stats

LanguagePython

Stars0

MaintenanceExcellent

Last CommitApr 22, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Post-Session Reflection

Use this skill when the user signals the session is winding down (phrases like "wrap up", "what did we do", "summarize", "done for today"), or immediately after a multi-tool research collage that warrants a recap.

Output format — exactly three bullets

- **Produced**: <artifacts — tool outputs, files, commits, plan docs> - **Decided**: <non-obvious choices made this session, with the reason> - **Next**: <explicit next step, owner, and trigger condition>

Rules

Three bullets, no more, no less. If you cannot compress to three, drop the least important item; do not add a fourth.

Each bullet is one sentence. Long bullets hide decisions.

"Produced" stays concrete — link file paths and commit SHAs when they exist, not abstractions.

"Decided" favours the non-obvious. Trivial defaults ("we used the default timeout") do not belong here. A fork in the road does.

"Next" is actionable. A task the next session can pick up without re-reading the transcript. Include the trigger (e.g. "when BTC >= $X" or "before PR #Y merges").

Example

- **Produced**: `MetricsDecorator` + `HealthMonitor` (commits b7c6991, bb1b8aa) and 24 new unit tests in `tests/unit/observability/`. - **Decided**: Prometheus-compatible dict snapshot over text format for now — keeps the surface JSON-serialisable until we add the HTTP endpoint in Phase 2. - **Next**: Wire `HealthMonitor.start()` into `build_production_service` and expose `venue_health_check_total` via `/cryptozavr:health` when Supabase is reachable again.

When NOT to use

Mid-session debugging (use venue-debug instead).

Quick Q&A where no artifacts were produced.

Planning sessions — use the feature-dev skill's plan format there.