Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By cosmicdreams
Sprint retrospective infrastructure: agent interviews via SubagentStop hook, session analysis, action cards, and retrospective kanban board.
npx claudepluginhub cosmicdreams/claude-plugins --plugin retroRetro interview standard for sprint agents. Use when an agent receives a "Shutdown imminent" message from team-lead, when manually triggering agent self-documentation before shutdown, or when verifying interview coverage after a sprint. Agents follow this skill to write their own interview file before confirming shutdown readiness to team-lead.
Manages the retrospective-actions kanban board — creating, reviewing, approving, deduplicating, and moving improvement cards in .beads/retro.db. Invoke when asked to "create a retro card", "approve an action card", "review retro cards", "scrum retro cards", "work the retro backlog", or "show retro board". Required reading before any operation on the retrospective board. Pairs with sprint:kanban for universal rules. Do not use for sprint-run board operations — those use sprint:kanban directly.
Runs a structured end-of-sprint retrospective that reads stored agent interviews, mines JSONL transcripts for metrics, interviews the user, and generates a report with actionable improvement cards. Invoke when the user says "run retrospective", "session review", "what worked and what didn't", "capture learnings", or "end of sprint review". Also invoke after all agents have shut down and sprint work is complete. Do not invoke mid-sprint while agents are still active, for individual issue reviews, or for status checks — those are not retrospectives.
Retrieves and summarizes a sprint agent's JSONL session transcript, showing tool calls, errors, messages, and retry patterns. Invoke when asked to "read the transcript for implementer-1", "what did agent X do", "show me the agent log", "analyze what happened during task 25", or "retrieve agent session". Also invoke when a process-observer or team-lead needs to review agent behavior after task completion. Accepts --teammate, --task, --focus, and --session arguments. Do not use for reading kanban cards, analysis reports, or non-JSONL files — use Read tool directly for those.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Memory compression system for Claude Code - persist context across sessions
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Curate auto-memory, promote learnings to CLAUDE.md and rules, extract proven patterns into reusable skills.
Team sprint execution infrastructure: agents, skills, hooks, protocols, and kanban pipeline.
Plugin, agent, and skill management tooling: bump-version, scaffold, new-agent, new-skill, optimize-agents, update-plugins, create-worktree.
Pre-work ideation with a visual decision canvas. Generates divergent ideas, launches a local web UI for human annotation, then synthesizes decisions into a concrete plan.
Drupal-specific development skills and agents (DDEV, Analysis, Validation, Scaffolding).
Automated Drupal and WordPress error monitoring and self-healing pipeline: watches logs (DDEV + Acquia), triages errors into curated Beads tickets, autonomously implements fixes in isolated git worktrees, captures verified Actual solutions alongside Projected hypotheses, and surfaces past fixes via /drover:recall.
A collection of Claude Code plugins covering team sprint orchestration, Drupal development, process engineering, passive knowledge capture, and meta-tooling for plugin authoring.
Several plugins require external CLI tools (Beads, Obsidian CLI, GitHub CLI, jira-cli, ddev, etc.).
→ See DEPENDENCIES.md for the full install guide.
# Clone the repo
git clone git@github.com:cosmicdreams/claude-plugins.git
cd claude-plugins/worktrees/main
# Install plugins at user scope
claude plugin install admin@local --scope user
claude plugin install sprint@local --scope user
claude plugin install retro@local --scope user
claude plugin install ideate@local --scope user
claude plugin install drupal-lab@local --scope user
claude plugin install lib@local --scope user
claude plugin install workflow@local --scope user
claude plugin install drover@local --scope user
claude plugin install research-lab@local --scope user
claude plugin install improve@local --scope user
claude plugin install ideas-funnel@local --scope user
After installing, initialize the sprint board in your project:
brew install beads
bd init --prefix sprint
adminMeta-tooling for developing and maintaining Claude Code plugins.
Skills: agent-team, bump-version, changelog, create-worktree, install, new-agent, new-skill, optimize-agents, scaffold, scaffold-silence, update-plugins
sprintTeam sprint execution: parallel agents, kanban pipeline, hooks, protocols.
Skills: asset-audit, board, kanban, plan, project-notes, run
retroEnd-of-sprint retrospectives: agent interviews via SubagentStop hook, action card management, session reports.
Skills: interviews, kanban, session, transcript
ideatePre-work ideation: brainstorm canvas, deep research, structured comparison, reality checks, diagrams, ADRs.
Skills: adr, brainstorm, compare, diagram, reality-check, research, understand
drupal-labDrupal development against DDEV: issue analysis, patch validation, contrib module scaffolding, performance profiling.
Skills: analyze-issue, browse-drupal-issues, config, ddev, finish-issue, issue-summary, module-dev-starter, perf-measure, process-lifecycle, validate-patch
libThin CLI-wrapper skills (data-layer only — no summarization). Slack, Jira, GitHub, TestRail, Obsidian vault, logs, and media utilities.
Skills: archive, csv-analysis, ddev, ffmpeg, github, hyperfine, image-optimize, jira, lighthouse, log-analyzer, pa11y, slack, testrail, vault-search, vault-store, wiki-query
workflowProcess automation built on top of lib: morning brief, deploy checklist, cross-source pulse, Obsidian maintenance, calendar/email helpers.
Skills: config, deploy-post, ecosystem-pulse, morning-brief, obsidian-lint, organize, personal-calendar, personal-email, pulse
droverAutomated Drupal error monitoring and self-healing pipeline. Watches logs, triages errors into curated Beads tickets, autonomously implements fixes in isolated git worktrees, notifies on ready-for-review.
Skills: add-project, backfill, baseline, board, dashboard, implement, reset-state, run, setup, triage, watch
research-labComposable research engagement pipeline: literary review via NotebookLM, multi-agent workshop swarms, cross-examination seminars, and iterative experimentation with ratchet-based optimization.
Skills: experiment, literary-review, run, seminar, workshop
improveProcess engineering methodology. Maps process topology, makes directed fixes, runs improvement experiments, accumulates lint rules. Domain-agnostic — each plugin can own its own :improve skill for domain-specific knowledge.
Skills: accessibility-scan, attach, experiment, fix, lint, perf-measure, self
ideas-funnelPassive knowledge capture pipeline — Karpathy-derived LLM Wiki with Monitor-driven multi-domain ingest. Feeds land in Raw/, agents compile them into a cross-linked Obsidian wiki, memory evolves via confidence decay and graph-aware consolidation.
Skills: ingest, init, lint, query
admin:changelog <plugin> # e.g. admin:changelog sprint
admin:changelog <plugin> --latest # most recent version only
Chris Weber