Skip to content

feat: close superpowers gaps — anti-rationalization, status protocol, multi-platform#18

Open
bdfinst wants to merge 15 commits into
mainfrom
superpowers
Open

feat: close superpowers gaps — anti-rationalization, status protocol, multi-platform#18
bdfinst wants to merge 15 commits into
mainfrom
superpowers

Conversation

@bdfinst
Copy link
Copy Markdown
Owner

@bdfinst bdfinst commented Apr 16, 2026

Summary

Closes gaps identified in competitive analysis against obra/superpowers. 10 slices:

  • A: Anti-rationalization knowledge file with cross-cutting LLM rationalization patterns
  • B: Receiving-code-review skill (verification gates, YAGNI check, banned performative phrases)
  • C: Pressure testing + CSO checklist in skill authoring; agent-eval pressure fixture support
  • D: Debugging supporting files (root-cause tracing, condition-based waiting, find-polluter)
  • E: Subagent status protocol (DONE/DONE_WITH_CONCERNS/NEEDS_CONTEXT/BLOCKED) across 7 prompt templates, orchestrator, and build command
  • F: Testing anti-patterns reference + TDD cross-references
  • G: Worktree language-specific dependency install and baseline test verification
  • H1: Windows hooks (run-hook.cmd shim, install.ps1, TMPDIR fixes)
  • H2: Gemini CLI extension (manifest, GEMINI.md, 5 TOML commands)
  • H3: OpenAI Codex (AGENTS.md, .codex/ config, install guide)

Also rewrote quality-reviewer.md from direct reviewer to dispatcher, eliminating overlap with naming-review, structure-review, complexity-review, test-review, and security-review.

Quality Gate

  • [n/a] Tests: documentation/configuration changes only
  • Spec consistency gate: passed (10 slices, 53 BDD scenarios)
  • Plan review: 4 personas approved
  • Cross-references: 44/44 valid
  • Format validation: JSON + TOML parsers pass
  • Token budgets: all constrained files within limits

Test Plan

  • Verify hooks still work on macOS/Linux
  • Verify gemini-extension.json and .codex/config.toml parse correctly
  • Spot-check GEMINI.md and AGENTS.md for Claude Code-specific references
  • Verify plugin loads in Claude Code

🤖 Generated with Claude Code

bdfinst added 15 commits April 16, 2026 09:31
Competitive analysis comparing agentic-dev-team against obra/superpowers
identified gaps in anti-rationalization techniques, code review reception,
skill authoring depth, debugging references, subagent status codes, TDD
depth, and worktree setup. Specs cover 7 core implementation slices (A-G)
plus 3 platform support slices (H1-H3: Windows hooks, Gemini CLI, OpenAI
Codex). Multi-platform research document recommends graceful degradation
with platform-specific manifests reusing existing skills.

Removes completed/obsolete spec files from prior work.
18-step plan covering 10 slices (A-G core improvements, H1-H3 platform
support). All four plan review personas approved. Acceptance critic
blockers resolved: binary-verifiable criteria, parser validation commands,
deterministic DONE_WITH_CONCERNS branches.
Slice A: Anti-rationalization knowledge file + quality gate references
Slice B: Receiving-code-review skill with verification gates
Slice C: Pressure testing + CSO checklist in skill authoring guide
Slice D: Debugging supporting files (root-cause tracing, condition-based
waiting, find-polluter bisection)
Slice H1: Windows hooks shim (run-hook.cmd), install.ps1 prereq checker,
TMPDIR fixes in tdd-guard.sh and version-check.sh
Steps 7-8: Create implementer, spec-reviewer, and quality-reviewer
prompt templates with full behavioral content and status blocks
Step 9: Add status field to all 4 plan review templates
Step 10: Add Subagent Status Protocol section to orchestrator
Step 11: Add status handling to build command step 4
Create testing anti-patterns reference file. Add cross-reference from
TDD catch-all line to anti-rationalization knowledge. Add testing
anti-patterns loading note to implementer prompt.
…ewer overlap

Slice G: Create worktree-setup knowledge file with language detection
table. Add Worktree Setup section to implementer prompt. Reference
worktree setup in orchestrator Phase 3.

Fix: Rewrite quality-reviewer from a direct reviewer to a dispatcher
that selects and runs specialized review agents based on what changed.
Eliminates overlap with naming-review, structure-review, complexity-review,
test-review, and security-review agents.
Slice H2: Gemini CLI extension manifest, GEMINI.md context file,
5 TOML commands, hooks-gemini.json placeholder
Slice H3: AGENTS.md for Codex, .codex/config.toml, .codex/hooks.json
placeholder, CODEX-INSTALL.md setup guide

Both platforms reuse existing skills/ and knowledge/ without forking.
Capability limitations documented in each platform context file.
Skills: 31→32 (+receiving-code-review)
Knowledge files: 6→8 (+anti-rationalization, +worktree-setup)
Prompt templates: 8→7 (removed stale plan-reviewer.md reference)
Supporting reference files: +4 (testing-anti-patterns, root-cause-tracing,
condition-based-waiting, find-polluter)
Skills-by-phase: add receiving-code-review to Review phase
Add subagent status protocol reference to Multi-Agent Collaboration
- docs/skills.md: add 4 missing skills (receiving-code-review,
  static-analysis-integration, domain-analysis, js-project-init),
  remove stale plan-reviewer reference, update quality-reviewer
  description to "dispatcher"
- docs/agent_info.md: add prompt templates section for implementer,
  spec-reviewer, and quality-reviewer
- CLAUDE.md: skill count 32→33 (+js-project-init)
- GEMINI.md + AGENTS.md: skill count 31→33
- agent-registry.md: add js-project-init, remove stale plan-reviewer
The team-agents.svg was showing 10 agents but there are 11 —
ADR Author was missing. Added to center column below Product Manager.
Rename agent and command files, update all 14 references across the
plugin (CLAUDE.md, GEMINI.md, AGENTS.md, agent-registry, context-loading,
ci-debugging, performance-benchmark, security-engineer, benchmark command,
agent_info docs, team-agents diagram, GETTING-STARTED guide).
New knowledge file: contract-testing.md defines the two-layer validation
pattern — test doubles in the deterministic pipeline, integration tests
to validate the doubles against real dependencies.

TDD skill: replace "mocks only when unavoidable" with "validated test
doubles at architectural boundaries, real code for internal modules."

testing-anti-patterns: rewrite #5 from "integration tests as afterthought"
to "unvalidated test doubles" — the real anti-pattern is doubles without
integration tests that verify them, not the use of doubles itself.

Source: https://beyond.minimumcd.org/docs/testing/contract/index.html.md
Add all Claude Code tools to the allow list so the plugin operates
without permission prompts. Narrow deny rules from broad patterns
(rm *, git push *) to only truly irreversible operations (rm -rf,
force-push).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant