Suraj1235/open-dynamic-workflows / .agents/skills/ultracode
ultracode
VerifiedUltracode-style dynamic workflows for Zed Agent and zcode. Use when the user says "ultracode", "workflow:", "/deep-research", or wants broad multi-file work with planning, parallel execution, verification, or crash-resume.
Ultracode Through Open Dynamic Workflows for Zed Agent and zcode
Use this skill when the user invokes /ultracode, says ultracode, says workflow:, or asks for large coding work that benefits from explicit planning, parallel agents, verification, budgets, or crash-resumable execution.
The ODW context server should already be available from .zed/settings.json. The bridge scripts referenced below live next to this skill in scripts/.
Step 0: Check the daemon
Run:
node scripts/daemon-bridge.js --check
- Exit 0: use the daemon path.
- Exit 1 with auth guidance: tell the user to copy
~/.odw/daemon.tokenintoODW_DAEMON_TOKENor the host setting. - Exit 1 because the daemon is offline: tell the user to run
odw-daemon start, thenodw-daemon doctor zedorodw-daemon doctor zcode.
Daemon Path
- Prefer MCP/context-server tools when available: call
odw_health, thenodw_runfor direct execution orodw_planfirst when the user wants to review the plan, the task is expensive, or mutation risk is high. - If tools are unavailable but the daemon is reachable, use the local bridge:
node scripts/daemon-bridge.js plan "<task>"node scripts/daemon-bridge.js exec plan.jsonnode scripts/daemon-bridge.js status <workflowId>node scripts/daemon-bridge.js result <workflowId>
- Report the workflow id, topology, agent count, cost/time estimate, and final synthesized result. Do not redo the same work manually while ODW is running it.
Zed Agent and zcode Native Fallback
If the daemon is unavailable, state that full ultracode requires the daemon, then use the native planning and editing flow in Zed Agent or zcode: discovery -> parallel work -> adversarial verification -> synthesis.
Never include secrets in prompts, plans, logs, or workflow artifacts.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |