hyper-explore

Scan a repository and generate exploration.md with findings and an approach.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly understand what a Hyper task aims to achieve by surfacing end goals, scanning the codebase for relevant files, and framing a clear exploration artifact to guide implementation.

Core Features & Use Cases

  • Surface end goals from task context
  • Scan the repository for relevant files and patterns
  • Produce an exploration.md with Findings and Approach
  • Ready for user approval to continue the plan

Quick Start

Invoke the explore phase to clarify goals, audit the repository for relevant files, and generate exploration.md with findings and a recommended approach.

Frequently Asked Questions about hyper-explore

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

FAQPage Schema
How do I clarify task goals and map repository scope before implementation?

Codebase analysis for task management clarifies project goals and scans the repository to surface relevant files and patterns. It generates an exploration.md artifact with findings and a proposed approach to guide implementation.

What is an exploration artifact in AI agent task workflows?

An exploration artifact is an exploration.md file documenting repository findings and a recommended approach. It frames AI agent tasks by clarifying end goals and scoping the codebase before implementation begins.

How do I generate an exploration.md file for my codebase?

To generate an exploration.md file, invoke the explore phase to audit your repository for relevant files and patterns. The process outputs findings and a recommended approach ready for user approval.

Can I use codebase analysis to frame tasks for any repository?

Yes, codebase analysis scans any repository to surface relevant files and patterns. It clarifies task context and end goals, producing an exploration.md artifact regardless of the specific codebase structure.

What's the best way to document findings and propose an approach for a new task?

The best way to document task findings is to generate an exploration.md artifact. It captures repository scan results, surfaces end goals, and proposes a structured approach for fast approval and progression.

When should I not use automated codebase exploration for task framing?

Automated codebase exploration may be unnecessary for trivial tasks with minimal scope or when the repository structure is already thoroughly documented and the end goals require no clarification.