porada/domfiles / skills/.domfiles-super-flow
super-flow
VerifiedCoordinate a team of agents to carry out an agreed plan.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 744 B |
| references/super-flow.md | markdown | 17.0 KB |
| references/team-defaults.md | markdown | 969 B |
| references/team-member-instructions.md | markdown | 2.9 KB |
references/team-defaults.md
View on GitHub# Team Defaults
## Profiles
Keep your own model and effort as coordinator. By default, use Claude Opus for engineers, Codex Astra for the editor, and Codex Daybreak for a security engineer. Daybreak is costly for what it delivers, so use that role sparingly. Use `xhigh` effort for every team thread you create.
Resolve models against the current catalog in the invoking thread’s T3 environment. Honor the user’s model and effort overrides. For an unpinned model, select the newest version in its family, searching the catalog if the listing is partial. If a selected model or effort is unavailable, bring that choice to the user. Act as editor yourself only if you run the selected editor model. Otherwise create a separate editor thread.
## Names and Titles
Give every member, including the coordinator, a short name unique within the team. Use the invoking thread’s title as the flow title. Title each new member thread `⤷ <Role> <Name>: <flow title>`.
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: 472k | 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 |