explore

Coordinate bead-based exploration workflows for topic research and planning.

8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jfmyers9/claude --skill explore-jfmyers9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore
Source: https://github.com/jfmyers9/claude/tree/main/skills/explore
Command: npx skills add https://github.com/jfmyers9/claude --skill explore-jfmyers9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Research topics, investigate codebases, and create implementation plans within a beads-driven workflow, ensuring results are stored in the beads design field for traceability.

Core Features & Use Cases

  • Orchestrates exploration via beads workflow and Task delegation.
  • Stores findings inside beads (design field) rather than filesystem, enabling centralized collaboration.
  • Supports "New Exploration" and "Continue Exploration" paths to spawn agents and track progress.

Quick Start

Provide a topic to /explore to start a bead-based exploration and have the system spawn a Task bead with guided next steps.

Frequently Asked Questions about explore

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

FAQPage Schema
How does a bead-driven workflow store codebase research findings?

Bead-based exploration stores all research findings inside the bead design field rather than the filesystem, enabling centralized collaboration. This approach uses frontmatter-driven triggers and task-spawn automation to manage and track architectural planning tasks.

How do I start a new exploration workflow for a software project?

To start a new exploration, provide a topic to the system to trigger a bead-based workflow. The system will spawn a Task bead with guided next steps to automate your codebase investigation and topic research.

When do I need automated task spawning for architectural planning?

Automated exploration is ideal for investigating complex software projects and creating detailed implementation plans. It is specifically designed for architectural planning tasks and codebase investigations where traceability of findings is critical.

Are there limitations to storing exploration findings in the bead design field?

Storing findings in the bead design field rather than the filesystem centralizes collaboration but limits access to bead-compatible environments. This approach requires strict governance and standardized bead designs to maintain research traceability.