Goal: Move the standalone obra/drill skill-compliance benchmark into superpowers as a top-level evals/ directory, delete redundant bash tests under superpowers/tests/ after per-file subagent verification of drill scenario coverage, and update top-level docs so contributors land on the new structure. Architecture: Single PR against dev on a new branch f/evals-lift.
Goal: Make SDD's durable-progress workspace plan-scoped (.superpowers/sdd/ /) with a self-identifying ledger and end-of-plan cleanup, so a follow-up plan can never collide with a previous plan's artifacts and resumed controllers stop paying a forensic disambiguation tax. Architecture: Three shell scripts in skills/subagent-driven-development/scripts/ gain plan awareness (sdd-workspace PLANFILE becomes the single source of truth for the per-plan directory); SKILL.md's Durable
Goal: Make subagent-driven-development's review-fix loop convergent and autonomous (resume-the-implementer fix rounds, scoped re-reviews, five-round breaker, controller adjudication) and reorganize its SKILL.md by lifecycle — with quorum eval evidence. The superpowers repo (branch sdd-fix-loop-redesign, already created; spec committed) gets the skill restructure: one new prompt template, two template edits, one reference edit, and the SKILL.md rewrite whose full text is in Ta
This guide explains how to add support for a new harness — an IDE, CLI, or agent runner that isn't Claude Code — so that Superpowers skills auto-trigger there the same way they do natively. Part 1–3 explain how the system works and how to tell whether a harness can be supported at all; read these before you touch anything.
Goal: Move the standalone obra/drill skill-compliance benchmark into superpowers as a top-level evals/ directory, delete redundant bash tests under superpowers/tests/ after per-file subagent verification of drill scenario coverage, and update top-level docs so contributors land on the new structure. Architecture: Single PR against dev on a new branch f/evals-lift.
Goal: Make SDD's durable-progress workspace plan-scoped (.superpowers/sdd/ /) with a self-identifying ledger and end-of-plan cleanup, so a follow-up plan can never collide with a previous plan's artifacts and resumed controllers stop paying a forensic disambiguation tax. Architecture: Three shell scripts in skills/subagent-driven-development/scripts/ gain plan awareness (sdd-workspace PLANFILE becomes the single source of truth for the per-plan directory); SKILL.md's Durable
Goal: Make subagent-driven-development's review-fix loop convergent and autonomous (resume-the-implementer fix rounds, scoped re-reviews, five-round breaker, controller adjudication) and reorganize its SKILL.md by lifecycle — with quorum eval evidence. The superpowers repo (branch sdd-fix-loop-redesign, already created; spec committed) gets the skill restructure: one new prompt template, two template edits, one reference edit, and the SKILL.md rewrite whose full text is in Ta
This guide explains how to add support for a new harness — an IDE, CLI, or agent runner that isn't Claude Code — so that Superpowers skills auto-trigger there the same way they do natively. Part 1–3 explain how the system works and how to tell whether a harness can be supported at all; read these before you touch anything.