By qnurye
Divergent planning — explore multiple implementation directions for a goal, refine with user input, then generate executable launcher scripts for each chosen approach.
Validate detailed plans against their abstract direction and user goals within a diverge agent team. Reviews plans submitted by diverge-plan-writer teammates, checking for completeness, feasibility, and alignment. Approves or rejects with actionable feedback.
Implement code for a single phase within a diverge team. Implements autonomously, writes own tests, and reports completion status to Orchestrator.
Expand an abstract plan into a detailed implementation plan within a diverge agent team. This agent reads grounded context and an abstract direction, then produces a step-by-step detailed plan. After writing, it spawns a Devil's Advocate sub-agent for internal validation.
Audit whether the Phase 1 specification (context file with resolved decisions) is sufficiently clear and complete to proceed to Phase 2 abstract planning. Returns PASS or FAIL with specific gaps.
TDD verification agent for diverge teams. Writes integration/smoke tests in an isolated worktree (Phase A), then merges implementation, runs all tests, and performs code review (Phase B). Reports findings to Orchestrator.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Divergent planning skill for Claude Code. Given one goal, diverge explores
several implementation directions in parallel, refines them with you, and
emits one executable launcher script per approach so you can start the
implementation you like best in an isolated worktree.
/plugin marketplace add Qnurye/diverge
/plugin install diverge@diverge
/diverge <goal description or GitHub issue URL>
diverge runs through a six-phase state machine (grounding → clarifying →
abstracting → planning → reviewing → launching). At the end you get one
script per direction under /tmp/diverge/<goal-slug>/<direction-slug>.sh.
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1jq, git, and wt (worktrunk)
on your PATH. gather-context.sh checks these at Phase 0.skills/diverge/SKILL.md — state-machine orchestrator playbookPROTOCOL.md — signal definitions shared across the agent teamagents/diverge-*.md — 7 agents (plan writer, devil's advocate, spec
auditor, implementer, TDD writer/implementer/DA)scripts/*.sh — Phase 0 context grounding, Phase 5 launcher
generation, and worktree helper scriptsmonitor/ — optional observability UI (Bun server + HTML) that
surfaces live state during a diverge run; emits are best-effort and
the skill falls back silently if bun is not installednpx claudepluginhub qnurye/diverge --plugin divergeUltra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
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.