Skip to content

porada/domfiles / skills/.domfiles-super-flow

super-flow

Unverified

Coordinate a team of agents to carry out an agreed plan.

FileKindSize
SKILL.mdskill md744 B
references/super-flow.mdmarkdown23.9 KB
references/team-defaults.mdmarkdown1.0 KB
references/team-member-instructions.mdmarkdown4.0 KB

references/team-member-instructions.md

View on GitHub
# Team Member Instructions

You work in a team that the coordinator runs on one flow branch. Your assigned **unit** is a piece of work reviewed as a whole. A **checkpoint** is an interim commit of a unit’s work, and **landing** is the coordinator recording it on the flow branch. Once every unit clears review, **consolidation** is the coordinator’s one-time rewrite of the checkpoints into the final series.

## Work Within Your Assignment

Leave commits, landing work, running reviews, and creating team threads to the coordinator. As an engineer, you may use subagents for bounded work within the approved provider and disclosure scope. Notify the coordinator with `t3_thread_send` in `auto` mode. Send decisions about scope or design, approval needs, and any change of direction from the user to the coordinator. Raise blocking questions as soon as they arise. Before going idle, send the result of a finished assignment, even when it calls for no edits, or hand off the portion ready to land.

Engineers own code, test titles, and internal implementation comments, including `//` comments that don’t document a public API. The editor owns text surfaced to users, including runtime messages, documentation, and doc comments on public APIs. If describing the observed behavior would weaken an agreed guarantee, the editor brings the discrepancy to the coordinator before changing the wording. The editor also writes and revises the consolidated commit messages. The coordinator writes checkpoint messages.

You may consult anyone on the roster directly except the security engineer, who is costly. Bring security questions for them to the coordinator. For any other consult, name yourself as sender and use `t3_thread_send` with `mode: auto`. These consults ask questions without assigning work or requesting file changes and, unlike security consults, don’t count toward the concurrency ceiling. Say whether the answer blocks your work. Reply directly to a blocking consult. For other consults, answer in your own thread. When you initiate a non-blocking consult, read the answer in the recipient’s thread.

A safeguard block is your model’s or provider’s safety refusal of in-scope work. If you hit one, stop instead of rephrasing the request. Send the coordinator the refused request and the refusal in their exact wording, including any stated reason. Leave out anything outside the approved disclosure, and say what you left out. Don’t use anything from a consult to finish refused work.

## Prepare and Hand Off Changes

If you are an engineer in a private worktree, bring your branch up to the current flow tip before starting each unit or correction and again before offering each checkpoint, including a partial one. Preserve pending work, resolve conflicts in your worktree, and validate the integrated change. This includes catching up with editor and correction checkpoints. After consolidation, wait for the coordinator to move your branch onto the rewritten series before starting a final correction.

When a long check could overlap edits or hooks, run it in a task-directory copy of the source under test. Give the copy its own writable dependencies and outputs, and identify its source and build in your handoff.

When the coordinator steers an earlier correction into a newer unit, pause the newer work and make the correction first. Identify its paths or hunks separately from the work in progress. If they are inseparable, tell the coordinator and finish the newer unit for a combined checkpoint.

In your handoff, name the unit, the flow tip SHA your work sits on, the changed paths (including new untracked files), and validation evidence. Identify any edits outside the checkpoint and what remains if only part of the unit is ready. After sending, leave your checkout untouched, including scratch files, until the coordinator confirms the landing or asks you to catch up and resubmit. Hold even an assignment that arrives in the meantime. After a partial landing, resume the remainder when the coordinator releases it for edits.
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: 472kUpdated Claude CodeCodexUnverifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall