---
name: using-superpowers
description: General SEED work discipline for choosing project skills, planning only when useful, delegating deliberately, and validating before reporting.
version: 1.0.0
tags: [workflow, planning, delegation, verification, seed]
keywords: [skill, skills, plan, planning, delegate, delegation, verify, verification, implementation, research, debugging, report, workflow]
triggers: [start a task, substantial task, implementation task, research task, debugging task, review task, write a report]
agents: [lab-representative]
categories: [orchestration, planning, research, coding, verification, reporting]
---

# using-superpowers

Use this as a general work discipline inside SEED runs.

1. Check whether a project skill would materially improve the task. Prefer project skills over personal user skills so the run is reproducible.
2. Keep planning proportional. For tiny tasks, record the decision and act. For substantial tasks, create a short sub-plan with owner, evidence, verification, and stop condition.
3. Delegate when parallel expertise or independent verification helps. Give each member a clear mission, read/write scope, allowed tools, expected evidence, and completion condition.
4. Do not create duplicate work. If another member already owns a question or file path, follow up with that member or hold a team meeting.
5. Verify before reporting. Run the smallest meaningful check, cite evidence, then update progress and final report artifacts.
6. If a destructive or irreversible action appears useful, pause for professor approval instead of routing around it.

This skill is context, not a permission grant. Higher-priority OpenCode, SEED, team, workspace, and professor instructions always win.
