agent-factory
Creates specialized worker agents dynamically from templates. Use when orchestrator needs to spawn task-specific workers for…
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Claude Code
$ npx -y skills add Ibrahim-3d/orchestrator-supaconductor --skill verification-before-completion --agent claude-code
Codex
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill verification-before-completion -a codex -y
Cursor
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill verification-before-completion -a cursor -y
Gemini CLI
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill verification-before-completion -a gemini-cli -y
GitHub Copilot
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill verification-before-completion -a github-copilot -y
OpenCode
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill verification-before-completion -a opencode -y
Windsurf
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill verification-before-completion -a windsurf -y
name: verification-before-completion description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Claiming work is complete without verification is dishonesty, not efficiency.
**Core principle:** Evidence before claims, always.
**Violating the letter of this rule is violating the spirit of this rule.**
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the verification command in this message, you cannot claim it passes.
BEFORE claiming any status or expressing satisfaction: 1. IDENTIFY: What command proves this claim? 2. RUN: Execute the FULL command (fresh, complete) 3. read_file: Full output, check exit code, count failures 4. VERIFY: Does output confirm the claim? - If NO: State actual status with evidence - If YES: State claim WITH evidence 5. ONLY THEN: Make the claim Skip any step = lying, not verifying
| Claim | Requires | Not Sufficient | |-------|----------|----------------| | Tests pass | Test command output: 0 failures | Previous run, "should pass" | | Linter clean | Linter output: 0 errors | Partial check, extrapolation | | Build succeeds | Build command: exit 0 | Linter passing, logs look good | | Bug fixed | Test original symptom: passes | Code changed, assumed fixed | | Regression test works | Red-green cycle verified | Test passes once | | Agent completed | VCS diff shows changes | Agent reports "success" | | Requirements met | Line-by-line checklist | Tests passing |
| Excuse | Reality | |--------|---------| | "Should work now" | RUN the verification | | "I'm confident" | Confidence ≠ evidence | | "Just this once" | No exceptions | | "Linter passed" | Linter ≠ compiler | | "Agent said success" | Verify independently | | "I'm tired" | Exhaustion ≠ excuse | | "Partial check is enough" | Partial proves nothing | | "Different words so rule doesn't apply" | Spirit over letter |
**Tests:**
✅ [Run test command] [See: 34/34 pass] "All tests pass" ❌ "Should pass now" / "Looks correct"
**Regression tests (TDD Red-Green):**
✅ write_file → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass) ❌ "I've written a regression test" (without red-green verification)
**Build:**
✅ [Run build] [See: exit 0] "Build passes" ❌ "Linter passed" (linter doesn't check compilation)
**Requirements:**
✅ Re-read_file plan → Create checklist → Verify each → Report gaps or completion ❌ "Tests pass, phase complete"
**Agent delegation:**
✅ Agent reports success → Check VCS diff → Verify changes → Report actual state ❌ Trust agent report
From 24 failure memories:
**ALWAYS before:**
**Rule applies to:**
**No shortcuts for verification.**
Run the command. read_file the output. THEN claim the result.
This is non-negotiable.
Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills
Creates specialized worker agents dynamically from templates. Use when orchestrator needs to spawn task-specific workers for…
Simulate a 5-member expert board deliberation for major decisions. Use when evaluating plans, architecture choices, feature…
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.…
Use when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context…
Master coordinator for the Evaluate-Loop workflow v3. Supports GOAL-DRIVEN entry, PARALLEL execution via worker agents, BOARD OF…
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.