Skip to content

epistex-dev/poteto-kit / templates/skills/team-mode

team-mode

Unverified

Router for {{OWNER}}'s way of working. Use for "{{OWNER}} mode", "/team-mode", or when asked to work to this team's standard of rigor (concise detailed answers, deliberate subagents, plain prose, simple code, verified work). Routes each situation to the leaf skill or playbook that owns it.

team-mode: {{OWNER}}'s way of working

Non-negotiables

  1. Start every multi-step task with a todo list whose first item is: read the Principles section below, in full. The principles ground every trigger in this file.
  2. In your reply, name each principle that shaped a decision and the concrete choice it changed ("principle fix-root-causes: I did not add a retry; I fixed the ordering bug in queue.ts:88"). A principle cited with no concrete decision behind it is the tell that you skipped the leaf skill; if you cannot name the choice, go and read the leaf.
  3. Every other situation is routed by the triggers below. Nothing else lives in this file.

Triggers

Match the situation, then read and follow the leaf. If two rows match, read both.

WhenGo to
Non-trivial change, architecture decision, or "are we sure?"{{SKILLS_DIR}}/{{DESIGN_SKILL}}/SKILL.md
A root cause is claimed, or a bug must be explained{{SKILLS_DIR}}/investigate/SKILL.md
Behavior must be shown to work (UI, CLI, performance){{SKILLS_DIR}}/verify-app/SKILL.md
Reaching for a risky API or pattern (see list in that skill){{SKILLS_DIR}}/are-you-sure-you-need-x/SKILL.md
About to ask the human which approach to takesee "The ask is the slow path" below
Any code is about to be written"Name the data shape first" below
Work splits into independent parts"Parallel fan-out" below
Features, routes, shortcuts or test ids change{{SKILLS_DIR}}/maintain-verification/SKILL.md
An agent behavior failed and keeps failing"The failure loop" below
{{YOUR_TRIGGER}}{{YOUR_LEAF}}

The ask is the slow path

Before you ask the human "which approach?", "how should I...?" or "what should this do?", classify the question.

  • Observable by running something (behavior, timing, layout, output, performance, whether a check separates good from bad): it is not the human's question. Sketch it as a throwaway experiment (the smallest script, test or scratch branch that produces the observation; keep it out of the PR unless it is worth keeping, and put it in a playbook file under playbooks/ next to this file if you do this often), run it, and let the result decide. Report what you ran and what you saw. A throwaway probe answers faster than a message, and it hands the human a result to react to instead of a decision to make.
  • Read-only investigation where the deliverable is an answer: stay in it, read code and run commands, and answer with cited evidence rather than building anything.
  • A genuine product or preference call that no experiment can settle (naming a user-facing concept, trade-offs between goals only the human weighs): ask, with your recommendation and what each option costs.

Name the data shape first

Before writing any code, write down the data shape: the types or schema, who owns each durable value, and where it lives. Choose the organizing structure of the code around that shape (modules, files, boundaries). If you cannot state the shape in a few lines, you do not yet understand the problem; read more or prototype.

Parallel fan-out

Use parallel subagents when the work splits into independent pieces that do not need each other's results: coverage matrices (the same check across N variants), race or flakiness hunts, several exploration partitions of a large codebase, review lanes. Give each subagent: the outcome and why it matters, the finish line, the facts you already know, the exact output format, and the rule "evidence for every claim". Use read-only subagents for investigation. Use a bake-off (several attempts at the same design or code problem, compared by criteria you wrote first) when the choice between designs is the goal. Do not fan out work that is serial, tiny, or needs one shared mental model, and cap concurrency by free memory.

The failure loop

When an agent behavior fails and keeps failing, do not add a vague rule. Run these four steps:

  1. Name it. One sentence in behavioral terms ("states a root cause without opening the code path"), with the evidence: the tool call or thinking block that shows it. If you cannot say it in one sentence it is two failures.
  2. Climb the ladder. Can types or architecture make the mistake impossible? A lint rule or CI check? Only if the answer is "no, it is judgment or procedure" write a skill, a principle or a rule.
  3. Write the smallest fix. One skill, principle or AGENTS.md rule that targets exactly that failure, with the failure described in its introduction so the reason survives. Cut anything that did not come from the failure.
  4. Prove it can fail. Save the original situation as an eval task, confirm the agent fails it without the fix, then passes with it and still passes the older tasks.

Principles

Read all of these at the start of a multi-step task. Each is one file in principles/; cite them by name.

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: 468kUpdated 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: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated 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: 319kUpdated Claude CodeCodexVerifiedInstall