hyper-plan

Generates spec.md and T<N>.<M>-<slug>.md files from Chest. .md inputs.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyper-plan
Source: https://github.com/galatanovidiu/hyper7/tree/main/skills/hyper-plan
Command: npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex Hyper tasks often stalls teams waiting for a clear path from exploration to implementation. Hyper-plan automates the transition by converting an approved exploration into a formal spec and a set of vertical subtasks, ensuring alignment and traceability.

Core Features & Use Cases

  • Converts approved exploration into a detailed spec (spec.md) with acceptance criteria, edge cases, and a ToC-style index of subtasks.
  • Generates one T<N>.<M>-<slug>.md subtask file per vertical slice, stored at the task folder root with appropriate frontmatter and sections.
  • Enforces an approval gate before implementation and clarifies dependencies, writes ownership, and open questions as part of the planning workflow.

Quick Start

Describe the feature task in the task folder; Hyper-plan will generate spec.md and vertical subtasks.

Frequently Asked Questions about hyper-plan

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

FAQPage Schema
How do I convert an exploration document into a formal spec for task management?

To convert exploration into a formal spec, you provide approved exploration.md and task.md files. The planning workflow then generates a spec.md with acceptance criteria and a ToC-style index of vertical subtasks for traceability.

What is the best way to break down a feature scope into vertical subtasks?

The best way to break down feature scope into vertical subtasks is by generating per-slice T<N>.<M>-<slug>.md files. Each subtask file includes frontmatter and specific bodies, stored at the task folder root for clear ownership.

How do automated planning workflows handle approval gates before implementation?

Automated planning workflows handle approval gates by enforcing a formal review checkpoint after spec generation. The process sets an approval gate before implementation, ensuring team alignment on dependencies, open questions, and writes ownership.

Does this task planning approach work for general project management or only feature scopes?

This task planning approach works exclusively for feature scopes. It specifically applies to scope: feature, reading defined exploration inputs to produce formal specs and vertical subtask files, rather than handling general project management tasks.

What inputs are required to generate agile specs and subtask files?

Generating agile specs and subtask files requires exploration.md and task.md as inputs. These documents provide the approved context needed to output a detailed spec.md and structured T<N> subtask files with frontmatter.

Why does feature planning stall during the transition from exploration to implementation?

Feature planning stalls during the transition from exploration to implementation due to a lack of a clear, automated path. Converting approved exploration into formal specs and vertical subtasks ensures alignment and traceability, preventing workflow bottlenecks.