By codxse
A two-phase coding workflow: /case (planning model) defines the WHAT as a budget-solver contract; /solve (budget model) owns the HOW and executes it.
This skill should be used when the user asks to "plan a solution", "define a problem", "create a plan", "architect a solution", "let me plan this", or describes a coding task they want defined precisely before solving. Runs on a planning model (any frontier model, e.g. Opus/Sonnet/Fable/Mythos/Gemini Pro) as master architect — refuses to run on a budget model. Produces .case.md — a problem definition (the WHAT) that a cheaper solver model (/solve) consumes to do the HOW. If the scope is too large for a budget solver, the skill stops and asks the user to decompose or rescope. Also runs in refine-from-handoff mode: when .handoff.md exists (human rejection or solver pre-flight feedback), it improves .case.md accordingly (planning models only).
This skill should be used when the user asks to "solve the problem", "execute the plan", "implement the solution", "run the plan", or "start solving". Use only after /case has produced .case.md. Expected to run on a budget model (Haiku, Gemini Flash, or MiniMax-M3 via the `minimax` wrapper) but runs on any model — only warns (never blocks) if run on a planning model. Owns the HOW, pre-flights each slice before any code (too abstract / too big / ungrounded names → writes .handoff.md Type: pre-flight and STOPS without coding), executes one milestone per pass with test-first per slice, pauses for human verification on human/both slices, tracks progress in .solve-progress.md, and on rejection writes .handoff.md and STOPS for /case (any frontier model, e.g. Opus/Sonnet/Fable/Mythos/Gemini Pro) to refine the contract.
A Claude Code plugin marketplace by codxse. Currently ships two plugins:
| Plugin | Skills | Purpose |
|---|---|---|
case-solvers | /case, /solve | Two-phase coding workflow: architect contract → budget-solver execution |
writing-claude-md | /writing-claude-md | Write lean, high-signal CLAUDE.md / AGENTS.md context files |
/plugin marketplace add codxse/case-solvers
Then install whichever plugins you want:
/plugin install case-solvers@case-solvers
/plugin install writing-claude-md@case-solvers
case-solvers — Two-phase coding workflowA capable planning model acts as the architect and defines what to build; a cheap budget model acts as the solver and does how to build it.
/case — runs on a planning model — any frontier model (e.g. Opus / Sonnet / Fable / Mythos / Gemini Pro). Defines the problem precisely and writes .case.md: the requirement, boundaries, and acceptance criteria. Refuses to run on a budget model./solve — designed for a budget model (Haiku / Gemini Flash / MiniMax-M3). Reads .case.md, explores the codebase, picks the mechanism, and implements test-first — one milestone per pass.The two are a loop: when a slice is too vague or a human rejects the result, /solve writes .handoff.md and stops; /case reads it and refines the contract.
/case <problem description> # planning model → writes .case.md
# switch to a budget model (/model), then:
/solve # budget model → implements against the contract
Typical flow:
/case to turn a task into a precise, verifiable contract./solve to implement it test-first./solve writes .handoff.md (pre-flight gap or human rejection), switch back to a planning model and run /case again to refine, then resume /solve.These files are written into your working project (not this repo):
| File | Written by | Purpose |
|---|---|---|
.case.md | /case | The problem definition (the WHAT) — the contract. |
.solve-progress.md | /solve | Milestone/slice progress tracking. |
.handoff.md | /solve | Feedback to /case on rejection or pre-flight gap. |
writing-claude-md — Write lean project contextHelps you write CLAUDE.md and AGENTS.md that only include what can't be derived from the code. Teaches the litmus test: "Can an LLM learn this by reading the code?" — if yes, omit it.
/writing-claude-md
MIT © 2026 nadiar
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.
npx claudepluginhub codxse/case-solvers --plugin case-solversSkill for creating and updating CLAUDE.md and other LLM project context files. Teaches what to include, what to omit, and how to keep context lean.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Intelligent draw.io diagramming plugin with AI-powered diagram generation, multi-platform embedding (GitHub, Confluence, Azure DevOps, Notion, Teams, Harness), conditional formatting, live data binding, and MCP server integration for programmatic diagram creation and management.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.