Skip to content

v1.3.0 — Parallel Execution Hardening

Choose a tag to compare

@farshidghyasi farshidghyasi released this 21 Mar 21:41
· 80 commits to main since this release

What's New in v1.3.0

Addresses 10 critical parallel execution issues and adds behavioral guardrails inspired by the superpowers plugin methodology.

Parallel Execution Fixes

  • Import manifest generation — before each wave, scan completed task files and build a manifest of exact export names. Agents use correct imports instead of guessing.
  • Cross-agent import resolution — after parallel agents complete, verify imports match actual exports before merging.
  • Auto-commit worktrees — orchestrator auto-commits after each agent using only the task's declared files.
  • Shared file enforcement — unauthorized modifications to shared files (app.ts, routers, etc.) are automatically reverted before merge.

Post-Wave Verification

  • Integration smoke test — new integration_cmd quality gate runs after each wave. On failure, rolls back the entire wave and re-runs sequentially.
  • Wired status verification — automatically grep app entry points to verify wired: "yes" claims. Downgrades to pending if no import found.

Quality Gate Improvements

  • Diff mode — quality gates compare error counts against a baseline, so pre-existing failures don't mask new errors. New baseline_errors field in state.json.
  • Post-merge command verification — failures in post-merge commands are now blocking errors.
  • Wave numbering — Wave: field is now the sole source of truth; removed wave numbers from section headers.

Behavioral Guardrails (superpowers-inspired)

  • Rationalization prevention tables in spec-loop and spec-exec — every skippable step now has an explicit "you will think X, reality is Y" entry drawn from real production failures.
  • Verification iron law in spec-implementer and spec-tester — no completion claims without fresh evidence (grep output, test output, wiring chain confirmation). Tester independently verifies wired status instead of trusting implementer.
  • Structured 4-phase debugging in spec-debugger — replaces "fix it" with: Investigate → Analyze → Hypothesize → Implement. Requires root cause identification before any code changes. Includes red flags list for stopping and re-investigating.

Files Changed

  • skills/spec-loop/SKILL.md — parallel execution fixes + rationalization prevention
  • skills/spec-exec/SKILL.md — single iteration fixes + rationalization prevention
  • skills/spec-team/SKILL.md — team mode fixes
  • agents/spec-implementer.md — verification iron law + import manifest awareness
  • agents/spec-tester.md — independent wired verification + evidence requirements
  • agents/spec-debugger.md — 4-phase debugging methodology (rewritten)
  • agents/spec-tasker.md — wave numbering rule
  • references/quality-gates.md — diff mode + integration test documentation
  • templates/state.json — integration_cmd and baseline_errors fields
  • templates/tasks.md — updated template comment
  • CLAUDE.md — documented new concepts