Who it is forA product lead with several repos in one project who needs epics drafted from existing requirements.
The problemRequirements sit across many repositories, so turning them into epics means manual collection and rewriting.
The outcomeA governed draft run produces an epic plan that you answer in its session before any publishing step.
What you need first
- Node.js 22 or newer and npm 10 or newer
- A container runtime for jobs: Rancher Desktop, Docker, Podman, Colima or OrbStack
- At least one coding-agent CLI you already use, such as Claude Code or Codex
- A modern browser such as Chrome, Edge, Firefox or Safari on macOS
Steps
- Open the Product view at /product?project= for your project.
- Search the requirements list and select up to 40 requirements.
- Add an optional steer that tells the run what the epics should focus on.
- Choose Draft epics to launch the draft, review and approve run.
- Answer the plan and gate in the session that opens; publishing is not offered yet.
Prompt for your agent
In wicked-studio, open the Product view for project <project id>, select the requirements that mention <topic>, 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.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for mikeparcewski/wicked-studio and "Draft epics from a project's requirements"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer