feat(directives): scavenge superpowers plugin (using-superpowers, brainstorming, dispatching-parallel-agents, executing-plans): 6 directives

conductor/directives/skill_check_before_clarifying/meta.md

@@ -0,0 +1,8 @@
+# skill_check_before_clarifying
+
+## v1
+
+**Why this iteration:** Lifted from the global OpenCode superpowers plugin (obra/superpowers) — `skills/using-superpowers/SKILL.md`. The directive encodes the iron rule "Skill check precedes any response or action, even at 1% relevance" — including clarifying questions, file exploration, and shell calls. The Red Flags table (lines 79-95) is the canonical list of rationalizations the agent uses to skip this check.
+**Source:** superpowers plugin `skills/using-superpowers/SKILL.md:45-46` (Iron Rule) + `:79-95` (Red Flags table)
+
+**Lifted:** 2026-07-04 (scavenge sweep: superpowers plugin directives)

conductor/directives/skill_check_before_clarifying/v1.md

@@ -0,0 +1,31 @@
+# Skill check must precede any clarifying question, exploration, or action — even at 1% relevance
+
+## The rule
+
+Before any response (including clarifying questions, file reads, or shell calls), the agent MUST check whether any superpowers skill applies. If a skill applies, the agent invokes it first; only after the skill body has been read does the agent produce the response.
+
+A 1% chance a skill applies is enough to justify the check. The skill check is non-optional, non-deferrable, and not subject to "I'll do it after I get more context."
+
+Per `skills/using-superpowers/SKILL.md:45-46`: "**Invoke relevant or requested skills BEFORE any response or action.** Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it."
+
+## Why
+
+Skills encode workflows the agent has been trained to skip. The agent's training data biases toward "let me explore the codebase first" / "let me check git/files quickly" / "let me gather more context." All three patterns bypass the skill check; all three then run unguided. Producing the response without reading the skill produces output that the skill would have shaped differently.
+
+Per `skills/using-superpowers/SKILL.md:79-95` (Red Flags table), the rationalizations are exact:
+
+| Thought | Reality |
+|---------|---------|
+| "I need more context first" | Skill check comes BEFORE clarifying questions. |
+| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
+| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
+| "Let me gather information first" | Skills tell you HOW to gather information. |
+| "The skill is overkill" | Simple things become complex. Use it. |
+| "I remember that skill" | Skills evolve. Read current version. |
+
+## What this means in practice
+
+- Before writing any clarifying question, run a Skill-tool-equivalent check.
+- Before reading any file, run a Skill-tool-equivalent check.
+- Before running any shell command, run a Skill-tool-equivalent check.
+- Announce the skill invocation explicitly ("Using [skill] to [purpose]") per `skills/using-superpowers/SKILL.md:65-66` so the user / future-self can audit which skill was followed.