IDC workflow (Think → Plan → Build → Recirculator, drained by Autorun) — a guardrail-framed, tracker-driven, goal-contract development pipeline as an installable Claude Code plugin
IDC Autorun — one-shot full-pipe drainer (plan unplanned considerations, heal the board, build eligible waves)
IDC Build — execute goal-contract issues as goal loops, review via the merged engine, automerge on PASS
IDC health check — verify plugin scoping (no global leak), gh auth + project scope, the tracker board, the v2 scaffold, and plugin-cache freshness (read-only)
IDC Init — scaffold a repo for the v2 IDC pipeline (WORKFLOW.md, config with codebase-derived domains, 5-field board, install receipts)
IDC Plan — decompose an admitted consideration into goal-contract issues on the board (domain experts, matrix deconfliction); pure decomposition, no requirements authoring
IDC Autorun orchestrator playbook — the one-shot two-lane drainer: plan every unplanned consideration, heal the board, build eligible waves, exit when nothing actionable remains.
IDC Build orchestrator — drives the impl→review→finish triplet (implementer · combined review agent · finisher) as one logical worker per issue, serializes merges, and closes the wave.
The triplet's finisher role — runs its OWN /fullauto-goal loop over ALL reviewer findings, then /simplify + git finalization (merge under the serialized merge lock, tidy), and files a recirculation on the unsolvable.
The Build triplet's engine — claims an eligible issue and executes its goal contract as a /fullauto-goal loop, then hands off to review.
IDC Plan orchestrator playbook — consideration → goal-contract issues on the board, in one zero-teammate run.
Use when an IDC role running under Claude Code must turn an abstract runtime primitive (durable worker / bounded fan-out / goal loop) into concrete Claude mechanics, or resolve a model tier to a concrete model.
Use when an IDC role running under the Codex CLI must turn an abstract runtime primitive (durable worker / bounded fan-out / goal loop) into concrete Codex mechanics. Codex is untiered — highest model + highest effort for everything.
Use when an IDC role running under the pi / coms-net flat-peer runtime must turn an abstract runtime primitive (durable worker / bounded fan-out / goal loop) into concrete pi mechanics — standing coms-net residents, ephemeral child-process fan-out, and the board-backed merge lease.
Use when authoring or validating a /idc:think consideration file — the function-first, Plan-ready shape and its mechanical check.
Use to fire IDC's one human gate — requirements admission. Think uses it at the end of Think to gate a new PRD+TRD on the Think PR; the Recirculator reuses it when backflow needs a requirements change. Supports sync-or-async approval and draft-until-merge.
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.
A Claude Code plugin that carries software from a raw idea to merged, reviewed code —
a guardrail-framed, tracker-driven, goal-contract pipeline. Guardrails, not train tracks.
IDC is an autonomous, agentic software-development pipeline. You start an idea in Think; it crystallizes into a PRD (what it does) and a TRD (how it's built) and reaches the one gate — a reviewable Think PR you merge to admit it. From there the pipeline plans, builds, and reviews on its own and automerges when clean, merging finished code into your repo. It stops to ask you exactly one question, once, at the top: do you approve these requirements?
An idea enters Think, which crystallizes it into a PRD + TRD. The one gate is a Think PR you merge to admit it. Admitted work runs through planning — sliced into the matrix, screened by matrix analysis, fanned out by the sequencer into parallel waves — runs the build triplet (implementer → review → finisher), and reaches the ship-or-return decision: clean work merges and ships; anything not-good goes to the Recirculator — the one controlled way back, all the way to the gate.
→ The full mental model, part by part, lives in docs/mental-model.md.
IDC — the Iterative Development Cycle — is the pipeline in the picture above: a Think stage that feeds the one gate (a Think PR admitting the PRD + TRD), a planning stage, a build triplet (implementer → review → finisher), two gates (approval at the top; ship-or-return at the end), and one Recirculator for the controlled return path. Everything runs autonomously and automerges when green; the pipeline intervenes only where a real derailment would otherwise ship.
| Stage | Command | What happens | Writes |
|---|---|---|---|
| Think | /idc:think | Idea → the one gate — free brainstorm (zero teammates) → crystallize a function-first PRD + TRD → the Think PR gate (admit by merging). | docs/considerations/, docs/prd/, docs/specs/ |
| Plan | /idc:plan | Decomposition — admitted idea → goal-contract issues: domain experts, the matrix (domain × phase/wave), matrix analysis, the sequencer into parallel waves. Pure decomposition — no requirements docs, no gate. | docs/plans/, matrices, issues |
| Build | /idc:build | Implementer → review → finisher → ship-or-return — each issue's goal contract runs as an iterative loop; independent review screens every PR; automerge on PASS. | source, tests, review reports, tracker status |
| Recirculate | /idc:recirculate | The return path — the ship-or-return decision's way back: heals doc/reality drift in one PR (PR body = change order); a requirements change rides the Think-PR gate. | every affected canonical doc |
| Autorun | /idc:autorun | Runs the whole pipeline — turn it on and it works end to end on its own; loop it with /loop. | — |
Autorun runs the whole pipeline: admitted considerations → plan → build eligible waves as they land → exit when nothing actionable remains (an open Think PR is reported + skipped, never bypassed).
npx claudepluginhub llamallamaredpajama/idc-workflow --plugin idcComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
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
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Complete developer toolkit for Claude Code
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.