Menu
Converts a desired behavior, prompt, or idea into a properly formatted workflow file in the Hypergraph Coding Agent Framework. Use when the user wants to create a new slash command or workflow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Updates all project documentation after code or skill changes. Always reads actual implementation before writing. Covers README, CHANGELOG, docs/, AGENTS.md, memory files, and skills-info.md. Use after completing any feature, fix, refactor, or skill update.
Compacts the current conversation into a handoff document so a fresh agent can continue the work. Saves to the OS temp directory, not the workspace. Pass an optional argument describing what the next session will focus on.
Documents the process, methodology, and decisions of the current session as a reproducible narrative. Saves to spec/process/ in the workspace so the journey can be understood and recreated by others.
Scaffolds a new project by conducting an interview to collect metadata and generating standard repository documentation files from the framework templates. Use when setting up a new repository.
Run this after /hyper-tutorial-run to turn tutorial failures into a structured, constraint-aware goal prompt. Interviews the user about their goal and what may/may not be changed, then generates a paste-ready prompt for a new Claude Code fix session. Does NOT re-run tutorial commands.
Generates a markdown tutorial from an integration test or user-provided files through iterative LLM + human collaboration. Tutorials are saved to tutorials/<name>/ with organized supporting files.
| name | new-workflow |
| description | Converts a desired behavior, prompt, or idea into a properly formatted workflow file in the Hypergraph Coding Agent Framework. Use when the user wants to create a new slash command or workflow. |
This skill converts a description of desired agent behavior into a properly formatted workflow file, making it immediately available as a slash command.
/hyper-new-workflow [command_name] [description]./hyper-prompt-engineer completes and the user chooses to export as a workflow.Gather Inputs
Extract the command name and its intended behavior from the user's request.
If only a description is provided, suggest a short, hyphen-separated name (e.g., code-review, api-design).
Confirm a concise description for the frontmatter. Then use AskUserQuestion to confirm before drafting:
Confirm the command name and description?
- Option A: Looks good — proceed as suggested
- Option B: Change the name — specify a different name (use Other)
- Option C: Change the description — modify the description (use Other)
Draft the Skill File
.agents/skills/<command-name>/.agents/skills/<command-name>/SKILL.md---
name: <command-name>
description: <concise third-person description of what this skill does>
trigger: /<command-name>
---
## When to use this skill — trigger conditions## How to use it — numbered steps for the agent to follow. Be explicit about agent actions, not just outcomes.Create IDE Bridge Files
.claude/commands/<command-name>.md:
---
description: "<description matching SKILL.md>"
---
Read `.agents/skills/<command-name>/SKILL.md` and follow its instructions precisely.
.windsurf/workflows/<command-name>.md:
---
description: "<description matching SKILL.md>"
---
Read `.agents/skills/<command-name>/SKILL.md` and follow its instructions precisely.
Verify and Notify
/<command-name> skill is ready. The SKILL.md is the source of truth in .agents/skills/<command-name>/, with IDE bridges in .claude/commands/ and .windsurf/workflows/."