using-hymme

Maps hymme verification and workflow skills onto superpowers development phases.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Hakkadaikon/hymme --skill using-hymme-hakkadaikon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-hymme
Source: https://github.com/Hakkadaikon/hymme/tree/main/skills/using-hymme
Command: npx skills add https://github.com/Hakkadaikon/hymme --skill using-hymme-hakkadaikon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When using the hymme plugin alongside superpowers in Claude Code, it is unclear which hymme skill or agent should be invoked at each stage of the development workflow. This Skill provides the routing map that decides where hymme's verification skills (loop-engineering, test-design, formal-verification) and git/review workflow skills plug into superpowers' phases. ## Core Features & Use Cases - Phase-to-skill mapping: Directs which hymme skill to invoke during brainstorming, writing-plans, subagent-driven-development, debugging, and branch finishing. - Responsibility split: Clarifies whether superpowers or hymme owns each concern, such as commits (micro-commit), reviews (diff-review), PRs (pr-create), and history rewriting (rebase-flow / reset-flow). - Agent dispatch guidance: Specifies when the controller should dispatch hymme agents like coder, prover, modeler, and reviewers. - Use Case: At session start, before entering superpowers brainstorming for a concurrent state-machine feature, consult this Skill to learn that loop-engineering should run before the spec is finalized and test-design should run after spec approval. ## Quick Start Ask the AI to load the using-hymme skill at session start to determine which hymme skills and agents apply to each superpowers phase.

Frequently Asked Questions about using-hymme

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use hymme skills with superpowers in Claude Code?

Load the using-hymme skill at session start to get the injection map. It tells you which hymme skill to invoke before each superpowers phase, such as loop-engineering during brainstorming and test-design after spec approval.

When should I run loop-engineering or formal-verification during design?

Run loop-engineering during superpowers brainstorming when the design involves state transitions, concurrency, or ordering that can be finitized. Use formal-verification's property catalog for critical algorithms or security properties before the spec is finalized.

What is the difference between superpowers and hymme responsibilities?

Superpowers decides the engineering process phases, while hymme inserts verification and operations into each phase. For example, superpowers handles plan writing while hymme adds test-design T-ID ledgers, micro-commit for commits, and diff-review before PRs.

Which agent should implement tasks in subagent-driven development?

The hymme coder agent is the default implementer, following the ponytail minimalism principle and a TDD contract. Proof and model-checking work is dispatched separately by the controller to the prover and modeler agents.

Does using-hymme apply to dispatched subagents?

No. The skill explicitly instructs subagents dispatched for specific tasks to ignore it. It is intended for the main session controller that decides which skills and agents to invoke at each workflow stage.