# AI use cases for Wicked Studio (mikeparcewski/wicked-studio) Repo: [mikeparcewski/wicked-studio](https://github.com/mikeparcewski/wicked-studio) | Use cases: 4 | Page: https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/ wicked-studio is a browser UI for directing coding-agent CLIs (Claude Code, Codex, GitHub Copilot, OpenCode, Pi) as checked workers that run jobs in sandboxes behind verification gates. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Start a governed agent job from a chat plan: https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/direct-agent-job-from-chat/ - Approve agent changes using the assurance receipt: https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/approve-agent-work-with-evidence/ - Map a symbol's blast radius before changing code: https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/map-blast-radius-before-change/ - Draft epics from a project's requirements: https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/draft-epics-from-requirements/ ## How to start a governed agent job from a chat plan with Wicked Studio Repo: [mikeparcewski/wicked-studio](https://github.com/mikeparcewski/wicked-studio) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Describe a change in chat, confirm the proposed plan, and let agents run it in sandboxes. **Who it is for:** A developer with a repo and a coding-agent CLI who wants agents to make a change without watching a terminal. **The problem:** Coding agents start work without a clear plan, grade their own output and leave reasoning in a long scrollback. **The outcome:** A run starts only after you confirm the plan, and its progress appears in one session with gates you can answer. ### Steps 1. Run `npx wicked-crew serve` and open the URL it prints, by default http://127.0.0.1:7701. 2. Open the Agents tab and sign in each coding agent you want to use. 3. Choose New job, then Start with chat, and describe the change you want. 4. Read the plan the chat proposes and confirm it; nothing starts before you confirm. 5. Open the session at /s/:id and answer gate rows as they appear (approve, steer or reject). ### Prompt to paste into your agent ```text In the wicked-studio repo, use the Start with chat flow to describe a small change to , then confirm the proposed plan. Expected output: a session URL under /s/ with at least one gate row. Verify that the session header shows the assurance state before you approve any gate. ``` ### Caveat Studio shows gate outcomes and never grades the work itself, so you still review the diff and evidence before accepting a result. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/direct-agent-job-from-chat/ ## How to approve agent changes using the assurance receipt with Wicked Studio Repo: [mikeparcewski/wicked-studio](https://github.com/mikeparcewski/wicked-studio) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Check who built, evaluated and judged a change before you accept the delivery. **Who it is for:** A reviewer who must sign off on agent-written code and needs to know how it was verified. **The problem:** An agent's claim of done says little about whether another seat checked the work or what was skipped. **The outcome:** You accept, steer or reject each gate with the assurance receipt, transcripts, diffs and evidence bundle in hand. ### Steps 1. Open the run's session from the Desk so the gates that need you are listed first. 2. Open a gate row and read the assurance receipt: required checks, seats that ran, skipped checks and the tree and attempt. 3. Check the QE acceptance status shown on the session header, gate and delivery. 4. Open the transcript and the worktree diff viewer for the files that changed. 5. Download the evidence bundle, then approve, steer or reject the gate. ### Prompt to paste into your agent ```text In the wicked-studio repo, open the session for and review its assurance receipt and gate rows. Expected output: a short note stating the assurance label, whether the builder and evaluator were separate seats, and any skipped checks. Verify that the note names the QE acceptance state exactly as the UI shows it. ``` ### Caveat A run on a single seat is labelled Reduced assurance, so check the label before you treat the result as independently accepted. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/approve-agent-work-with-evidence/ ## How to map a symbol's blast radius before changing code with Wicked Studio Repo: [mikeparcewski/wicked-studio](https://github.com/mikeparcewski/wicked-studio) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Onboard a repo, then check what a change to one symbol would touch. **Who it is for:** A developer about to refactor shared code who wants to see its callers and risky hotspots first. **The problem:** Changing a widely used symbol without seeing its callers can break parts of the codebase nobody checked. **The outcome:** You have a list of affected code and hotspots to review before you start an agent run on the change. ### Steps 1. Run `npx wicked-crew serve` and open the studio URL it prints. 2. Register your repo by local path or by cloning its URL, then let studio build the code graph. 3. Open the graph view and search for the symbol you plan to change. 4. Check its blast radius and the hotspots list, then note the files to review. 5. Start a run on the change only after you have reviewed those files. ### Prompt to paste into your agent ```text Using wicked-studio, onboard the repo at and open the blast radius for the symbol . Expected output: a list of affected files and the hotspots in the same area. Verify that every file in the list appears in the graph view before you start any run. ``` ### Caveat The code graph is built by studio after onboarding, so results only cover the repo state at the time it was built. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/map-blast-radius-before-change/ ## How to draft epics from a project's requirements with Wicked Studio Repo: [mikeparcewski/wicked-studio](https://github.com/mikeparcewski/wicked-studio) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Pick requirements across repos and launch a governed draft run that opens in its session. **Who it is for:** A product lead with several repos in one project who needs epics drafted from existing requirements. **The problem:** Requirements sit across many repositories, so turning them into epics means manual collection and rewriting. **The outcome:** A governed draft run produces an epic plan that you answer in its session before any publishing step. ### Steps 1. Open the Product view at /product?project= for your project. 2. Search the requirements list and select up to 40 requirements. 3. Add an optional steer that tells the run what the epics should focus on. 4. Choose Draft epics to launch the draft, review and approve run. 5. Answer the plan and gate in the session that opens; publishing is not offered yet. ### Prompt to paste into your agent ```text In wicked-studio, open the Product view for project , select the requirements that mention , and choose Draft epics. Expected output: a session with a plan and a pending gate. Verify that the session lists only the requirements you selected. ``` ### Caveat Publishing drafted epics is not offered yet, so the draft still needs to be carried into your tracker by hand. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/draft-epics-from-requirements/