configurelisted

Set up dev-loop's capability-role tool profile — map `knowledge` (your domain wiki / MCP), `verify` (your project's test/build/QA command), `explore` (code search), `tacit` (past incidents), and `design` (Figma/visual spec) to the actual tools this environment has, then write ~/.claude/dev-loop/tools.json (global) or <repo>/.dev-loop/tools.json (per-repo). Use when asked to "configure dev-loop", "set up tools", "map my wiki/test command", or "/dev-loop:configure".
choiyounggi/dev-loop · ★ 4 · AI & Automation · score 80

Install: claude install-skill choiyounggi/dev-loop

# configure — set up the dev-loop tool profile dev-loop runs fully generic with **no** config (every role falls back to the model's own behavior). Configuring the roles makes the loop use *your* real tools: your domain wiki for facts, your actual test command for verification, etc. The bundled best-practice `wiki/` (used by `wiki-plan`) needs no config — the `knowledge` role is for a separate *external/domain* wiki. > Note: the plan step is fixed to `wiki-plan` and is NOT configurable. There is no > `plan` role. ## Steps 1. **Show the current profile.** Run and report what is already set vs. default: ```sh sh ${CLAUDE_PLUGIN_ROOT}/scripts/resolve-tools.sh --summary ``` 2. **Decide scope.** - **Global** (all your projects): `~/.claude/dev-loop/tools.json` - **Per-repo** (committed, team-shared; overrides global per role/field): `<repo>/.dev-loop/tools.json` Ask the user which, if unclear. (Legacy `~/.claude/loop-orchestrator/tools.json` and `<repo>/.loop-orchestrator/tools.json` are still read as a fallback.) 3. **Map each role to a real tool.** Read `${CLAUDE_PLUGIN_ROOT}/examples/tools.example.json` as the shape and `references/tool-profile.md` for the schema. For THIS environment, detect and propose concrete mappings, then confirm with the user: | Role | Map to | How to find it | |------|--------|----------------| | `knowledge` | your domain/policy **wiki** or knowledge MCP | check available MCP servers (e.g. a `wiki_search`/`