From 5a76563894ba62a60d74ea8705f83c02af8d8a27 Mon Sep 17 00:00:00 2001 From: Ed_ Date: Sun, 5 Jul 2026 13:11:10 -0400 Subject: [PATCH] =?UTF-8?q?conductor(track):=20superpowers=20review=20sect?= =?UTF-8?q?ion=201=20=E2=80=94=20using-superpowers=20(brief)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../superpowers_review_20260619/report.md | 42 ++++++++++++++++++- 1 file changed, 41 insertions(+), 1 deletion(-) diff --git a/conductor/tracks/superpowers_review_20260619/report.md b/conductor/tracks/superpowers_review_20260619/report.md index 7aa623c1..881ff19e 100644 --- a/conductor/tracks/superpowers_review_20260619/report.md +++ b/conductor/tracks/superpowers_review_20260619/report.md @@ -16,7 +16,47 @@ ## 1. Using Superpowers - +## 1. Using Superpowers + +### 1.1 What the skill prescribes + +The `using-superpowers` skill establishes the foundational "skill before action" discipline: invoke the Skill tool to load a relevant skill BEFORE any response or action — including clarifying questions. The skill's red-flag table is explicit: rationalizing that a skill is "overkill," "I'll just check files quickly," or "I'll gather information first" is a STOP signal. The skill flow is: receive message → check if any skill applies (even at 1%) → invoke the Skill tool → follow the skill exactly. Instruction priority is also locked: user instructions > skills > default system prompt. + +### 1.2 Mapping to the project's existing pattern + +Manual Slop's agent-directive corpus already encodes this discipline, but via file reads rather than a Skill tool: + +| Superpowers rule | Project equivalent | Where | +|---|---|---| +| "Skill before action" | "Session Start Checklist (MANDATORY)" — block progress until checklist is complete | `conductor/workflow.md` §"Session Start Checklist" | +| "Read the rules first" | AGENTS.md is the top-level entry point; it's literally the first file any agent reads | `AGENTS.md:1` ("Manual Slop is a local GUI orchestrator...") | +| "User instructions take precedence" | CLAUDE.md says "this project is no longer actively used with Claude Code. For project context, see AGENTS.md. The conductor system in ./conductor/ is the cross-tool abstraction and works with any agent toolchain." | `CLAUDE.md:1` | +| "Invoke skill, don't rationalize" | Hard ban list (git restore, git stash, day estimates, opaque types) — "If you think you need one, ASK FIRST." | `AGENTS.md` "Critical Anti-Patterns" | + +The 12-item Session Start Checklist (`conductor/workflow.md` §"Session Start Checklist") includes reading `AGENTS.md`, `conductor/workflow.md`, `conductor/tech-stack.md`, `conductor/product.md`, `conductor/product-guidelines.md`, the data-oriented design styleguide, the Python styleguide, the type-aliases styleguide, the error-handling styleguide, the relevant `docs/guide_*.md`, and `conductor/tracks.md`. This is the project's "skills catalog" — file-based rather than tool-based. + +### 1.3 Gaps + +- **No explicit "skill check before action" prompt in the Session Start Checklist.** The checklist is exhaustive but procedural; it doesn't say "announce which skill(s) you are invoking." For an OpenCode-based workflow this is fine (the user's session-start message itself triggers the mma-orchestrator + tier-1 skills per the skill activation protocol in `conductor/workflow.md` §"Conductor Token Firewalling"). For ad-hoc use of an agent in a fresh context, the checklist could explicitly include "announce which superpowers/agent skill(s) you are invoking" as item 13. +- **The skill file (`SKILL.md`) is a Claude Code concept.** Other environments (Gemini CLI, raw GPT) don't have a Skill tool. The project's file-based pattern is more portable. This is not a gap per se, but an architectural observation. +- **AGENTS.md is mandatory read; the conductor styleguides are mandatory read; `docs/guide_*.md` is "consult as relevant."** The skill hierarchy (skill > skill > skill) doesn't fully map to the project's tier-of-mandatory-ness. Section 16 (dual-convention) flags this. + +### 1.4 Recommendation summary + +The project follows the discipline. No code/spec changes recommended. The deferred rebuild may want to add the "announce which skill(s)" prompt to the Session Start Checklist for fresh-context agents. + +**Verdict.** + +| Field | Value | +|---|---| +| **Primary** | `PARITY` | +| **Integration tag** | `INTEGRATED` | +| **Section size** | brief | +| **Cross-refs** | nagent_review_20260608 §3.6 (instruction priority), fable_review_20260617 §14 ("Anti-User Watchdog Patterns") | + +**Rationale.** The project's Session Start Checklist + AGENTS.md + conductor/*.md + docs/guide_*.md pipeline is the file-based equivalent of the superpowers Skill tool. Both enforce "rules before action." The project already includes instruction priority (CLAUDE.md > AGENTS.md > system prompt) and a 12-item mandatory checklist. + +**Recommended change.** *(blank — no rebuild action.)* ## 2. Brainstorming