wind7rui/hyperspec

HyperSpec is an add-on for AI coding assistants like Claude Code, Cursor, and Codex CLI that ties together two other add-ons into one disciplined workflow. The first is OpenSpec, which manages specification documents: what you are going to build and why. The second is Superpowers, which manages test-driven development, planning, and code review by subagents. HyperSpec sits on top of both and does only four things: it senses what kind of project you have, checks current progress, routes the work to the right stage, and enforces a commit habit. The author is careful about scope. HyperSpec is described as a pure orchestration layer. It does not rewrite anything that OpenSpec or Superpowers already do. It does not create spec artifacts by hand, it does not convert tasks into plans by hand, and it does not run the archive step by hand. It calls those existing skills at the right moment instead. The same idea applies in reverse: it refuses to write code in the spec stage and refuses to edit specs in the implementation stage. A full run is split into three stages. The propose stage turns a vague user request into a proposal, a design document, a spec change set, a task list, and a step by step implementation plan with checkboxes. The apply stage executes that plan, picking between a full mode with subagents and a lightweight mode based on factors like task count and how many modules are touched. After each task it compiles, ticks the checkbox, updates state, and commits, but never pushes. The archive stage checks that the code matches the spec, calls the archive skill to merge the spec into the main spec library, and tidies the branch. Progress is tracked in a file called .hyperspec-state.yaml, and HyperSpec always verifies that file against the real project layout so a stale cache cannot mislead it. The project sensor reads file extensions and config files like pom.xml, package.json, go.mod, Cargo.toml, and pyproject.toml to pick the right build and test commands automatically. Installation is a copy of the folder into the skills directory of the editor you use.