wind7rui/hyperspec

This page was translated automatically. Technical details may differ from the original. View the original

77 stars Quality 64 Trend 18MIT

Overview

Specification-driven + engineering discipline complete development workflow skills, coordinating OpenSpec (specification management) and Superpowers (TDD + sub-agent review), completing the entire process from requirements to implementation to archiving. OpenSpec manages "what and why," while Superpowers manages "how to do it and whether it's done correctly." HyperSpec is **: mainly orchestrating OpenSpec/Superpowers (project awareness, state detection, stage routing, commit discipline), without overriding native skill functions; It also includes explicit enhancements such as specification consistency verification and plan quality review (not disguised as pure transparency). - : Automatically detects languages/frameworks/build tools, adaptively generates specifications and execution strategies - : Forces specification documentation to be generated before writing code, preventing AI from deviating from the direction of implementation - : Mainly orchestrates OpenSpec/Superpowers without overwriting their functions; Also includes explicit enhancements such as proprietary specification conformance verification - : Double-verification of structured state files + actual files, with precise recovery of any breakpoints - : Selects optimal execution mode based on multi-factor factors such as task count, dependencies, and cross-modularity - : Automatically adapts compilation and testing commands for different technology stacks such as Java/Node/Go/Rust/Python - Overlays CodeGraph (code structure layer) + Graphify (document knowledge layer) to provide structured retrieval of call chains/influence surfaces/historical specifications; Automatically reverts grep/Read when unavailable, core workflows do not rely on knowledge graphs Knowledge graph tools are optional enhancements. Usability is determined by **: indexed (index is present, project property) and tool_reachable (whether the tool can be adjusted in the current session, session properties), available = both true—using "directory at" to infer that "tool" is a category error (if the CLI is installed but the MCP is not paired, the directory is present but the tool is not reachable). When not installed or unavailable, the mark available: false automatically reverts grep/read, without affecting the main process; If any KG tool call returns "Unknown tool / tool does not exist / connection error" during runtime, it immediately declares unreachable, reverts grep/Read and sets tool_reachable to false, blocking "directory is present but MCP not injected → silent failure." (colbymchenry/codegraph, according to the official manual): Its MCP service** (single call returns source code + call chain + influence surface).

Overview (machine translated)

v1.1.0 · Update log

OpenSpec manages “what and why,” while Superpowers manages “how and whether it’s done correctly.” HyperSpec is a lightweight orchestration framework: mainly orchestrating OpenSpec/Superpowers (project awareness, state detection, stage routing, commit discipline), without overwriting native skill functions; It also includes explicit enhancements such as specification consistency verification and plan quality review (not disguised as pure transparency).

Core Values

Project Awareness: Automatically detects language/framework/build tools, adaptively generates specifications, and executes strategies
Demand First: Requires generating specification documents before writing code, preventing AI from heading off in direction
Lightweight orchestration framework: Primarily orchestrated with OpenSpec/Superpowers, without overriding its functions; Also includes explicit enhancements such as proprietary specification conformance verification
Breakpoint Recovery: Structured state files + actual files undergo double-verification, allowing precise restoration of any breakpoints
Intelligent Execution: Select the optimal execution mode based on multi-factor factors such as task quantity, dependencies, and cross-modularity
Multilingual support: Automatically adapts compilation and testing commands for different tech stacks such as Java, Node, Go, Rust, and Python
Knowledge Graph Awareness (optional): Stacks CodeGraph (code structure layer) + Graphify (document knowledge layer) to provide structured retrieval for calling chains, influence planes, and historical specifications; Automatically reverts grep/Read when unavailable, ensuring core processes do not rely on knowledge graphs

Upfront dependency

Dependencies	Uses	Inspection Methods	Installation Methods
Superpowers skill	TDD, Planning Writing, Sub-agent Development, Code Review	Check Brainstorming and Other Skills Availability	`/plugin install superpowers@claude-plugins-official`
OpenSpec CLI	Specification Document Management (Change Proposals, Design Documents, Task Splitting, Archiving)	Check if the project root directory has `openspec/`	`npx @fission-ai/openspec init`

Optional dependencies (knowledge graph sensing, automatically downgraded to grep/read when unavailable):

Dependency	Purpose	Availability Detection (Dual State)
CodeGraph MCP	Code Structure Layer: AST Parsing → Symbols/Call Chain/Dependency Graph/Influence Plane, Zero LLM Dependency	① `indexed`：`.

This page was translated automatically. Technical details may differ from the original.

Recommended Tools

Try a different keyword or remove a filter.

Install

npx skillfish add wind7rui/hyperspec

New to MCP? Start with the mcpskill.org guide →