explore

Guide developers to explore codebases and save structured findings as Markdown.

2|Updated Mar 10, 2026

Search Tags:#architecture #templates #documentation #codebase #exploration #explore

Ready to run

npx skills add https://github.com/tim-hub/powerball --skill explore-tim-hub

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: explore
Source: https://github.com/tim-hub/powerball/tree/main/pbl/skills/explore
Command: npx skills add https://github.com/tim-hub/powerball --skill explore-tim-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams frequently need a fast, repeatable way to understand a codebase, capture key insights, and reuse them for planning and onboarding.

Core Features & Use Cases

Guided discovery of a codebase or module to generate a structured, shareable summary.
Persistence of findings as a Markdown document in the specs repository for future reference and planning.
Supports architecture mapping, decision logging, and knowledge capture to accelerate onboarding and planning.

Quick Start

Start an guided exploration and save the results to the specs folder.

Frequently Asked Questions about explore

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

FAQPage Schema

How do I analyze a codebase and generate structured documentation for onboarding?▼

To generate structured documentation from a codebase, this Skill guides you through codebase exploration and captures key findings using a standardized Markdown template. It saves the resulting architecture summary directly into your specs folder for future reference.

What is the best way to map architecture and capture technical decisions in a codebase?▼

Architecture mapping and decision logging are handled through a guided exploration process that extracts structural insights from your codebase. The findings are formatted into a structured Markdown document for future planning and onboarding.

How do I save codebase exploration findings to the specs folder for future reference?▼

Saving codebase exploration findings requires writing the captured insights to a Markdown file within the specs directory. This Skill uses a defined file name and a frontmatter-based entry point to persist results under .powerball/specs.

Can I use this guided exploration for individual modules instead of a full codebase?▼

Yes, guided exploration can be applied to individual modules or a full codebase. It captures structured findings specific to the scope you select and saves them as a reusable Markdown document for future reference.

Does codebase exploration require any specific dependencies or environment setup?▼

Codebase exploration requires no external dependencies or specific environment setup. It operates internally by applying a frontmatter-based entry point and an exploration template to format and save your findings.