reflect
πPluginpandysp/claude-plugins
Capture durable lessons from a session before they fade: what surprised you, what friction repeated, what should update CLAUDE.md or notes. Output goes to memory, notes, or global instructions, not just to chat.
Part of
pandysp/claude-plugins
Installation
/plugin marketplace add pandysp/claude-plugins/plugin install reflect@pandyspMore from this repository10
Route Claude Code's auto-created git worktrees through worktrunk so background and --worktree sessions inherit project hooks (env symlinks, installs, port allocation).
Surface and resolve underspecified decisions before designing. Asks targeted questions about scope, edge behavior, trade-offs, integration, constraints, and audience (with defaults), so design choices aren't silently locked around hidden assumptions.
Multi-lens quality audit for docs, code, and other artifacts. 13 quality adjectives as audit lenses with per-domain translation sheets, a workflow-backed finder/verifier pipeline, and lens-yield reporting.
Systematically identify how a plan or design could fail before committing to it.
Write code, comments, tests, or commit messages that read as if the project's own maintainer wrote them, so a contribution is accepted as native rather than rejected as foreign. A foreign-looking patch is a cost to the maintainer even when it's correct.
Audit error handling for silent failures, inadequate feedback, and inappropriate fallbacks. Delegates to the silent-failure-hunter subagent for isolation
Map the terrain before designing: locate, trace, pattern, constrain. Used before any substantive design or planning step. Output is mostly for the agent's grounding; only surprises and hard constraints surface to the user.
Generate multiple strong design options with explicit tradeoff profiles, starting from the ideal architecture.
Black-box verification of any agent output: code, documents, presentations, reports, configs. Examine from the consumer's perspective and show evidence.
Write a durable handoff for work that's about to ship: structured PR descriptions, summaries, memos, or memory notes. Tells the next reader what was built, why, what changed, and what's next, without forcing them to dig through the diff.