epistex-dev/poteto-kit / templates/skills/team-mode
team-mode
UnverifiedRouter 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.2 KB |
| principles/_principle.template.md | markdown | 1.4 KB |
| principles/boundary-discipline.md | markdown | 946 B |
| principles/encode-lessons-in-skills.md | markdown | 957 B |
| principles/fix-root-causes.md | markdown | 892 B |
| principles/script-the-deterministic-parts.md | markdown | 1.3 KB |
principles/fix-root-causes.md
View on GitHub# fix-root-causes
**Rule:** Fix the cause of a problem where it originates, not the place where it shows up.
**Why:** A patch at the symptom (a retry, a null guard, a longer timeout) hides the defect, lets it recur through another path, and leaves the next person a worse system.
**In practice:**
- Before changing code for a bug, trace the wrong value or behavior back to where it first appears, and cite that `file:line` (skill `investigate`).
- If the true fix is larger than the task, say so and propose the split; do not ship the patch as if it were the fix.
- Remove the mechanism that allowed the bug when feasible (a type, a single writer) rather than adding a check beside it.
**Tells you are violating it:** new `try/catch` that swallows, retry loops, arbitrary sleeps, a special case keyed on the failing input.
**Enforced by:** soft: this file, plus the `investigate` skill.
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 |