skills.rest
shuu5
shuu5COMMUNITY
Explore all skills by this author →
GitHub

twl:co-explore

Manage interactive problem exploration and write summaries to .explore/<ISSUE_NUMBER>/summary.md.

Updated Apr 5, 2026
Search Tags:#automation#bash#issue-management#codebase-analysis#interactive-exploration#explore-summary
One-click install
npx skills add https://github.com/shuu5/twill --skill twl-co-explore
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: twl:co-explore
Source: https://github.com/shuu5/twill/tree/main/plugins/twl/skills/co-explore
Command: npx skills add https://github.com/shuu5/twill --skill twl-co-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomous, interactive problem exploration that engages users in a guided dialogue and saves the resulting explore-summary to .explore/<issue-number>/summary.md. It also connects to co-issue / co-architect workflows through Issue links.

Core Features & Use Cases

  • Interactive back-and-forth exploration with the user, producing a structured explore-summary.
  • Enforces a minimum of user interaction and prevents zero-shot exploration to ensure meaningful analysis.
  • Keeps exploration scoped to the initial phase; does not advance to issue refinement or creation tasks.
  • Acts as an interactive controller that can be initiated only via approved prompts (AskUserQuestion is not bypassable).
  • Provides a workflow for input analysis, codebase exploration, results visualization (ASCII diagrams), and result presentation for discussion.

Quick Start

Begin an interactive problem exploration with the user and save the resulting explore-summary to .explore/<ISSUE_NUMBER>/summary.md.

Frequently Asked Questions about twl:co-explore

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

FAQPage Schema
How do I explore a codebase interactively before creating an issue?▼

To explore a codebase interactively before creating an issue, this Skill guides you through a back-and-forth dialogue, searching code with Bash and Grep, then saving a structured summary to .explore/<ISSUE_NUMBER>/summary.md.

What is autonomous problem exploration in software engineering?▼

Autonomous problem exploration is an interactive process that engages users in guided dialogue to analyze a codebase, visualize results with ASCII diagrams, and produce a persistent summary file for later reference.

Can I use this interactive exploration to automatically generate and refine issues?▼

No, you cannot use this for automatic issue generation. It deliberately keeps exploration scoped to the initial analysis phase and prevents advancing to issue refinement or creation tasks.

Does interactive codebase analysis require zero-shot exploration?▼

No, interactive codebase analysis enforces a minimum of user interaction and explicitly prevents zero-shot exploration to ensure meaningful analysis and dialogue.

What tools are required to run autonomous codebase exploration?▼

Autonomous codebase exploration requires Bash, Read, Write, Grep, and Glob tools to search, read, and aggregate information across the codebase and write the final summary file.

How does interactive exploration connect to downstream issue workflows?▼

Interactive exploration connects to downstream workflows like co-issues or co-architect tasks by embedding Issue references within the generated explore-summary file for subsequent linking.

Related Skills

Explore More Software Engineering Skills→
Kushal9889Kushal9889

sync-gbrain

Synchronize the gbrain tool with repository code and refresh CLAUDE.md search guidance.

Community
Advanced
hmislkhmislk
224

commit-code

Generate HMIS-compliant commit messages with issue closing keywords and co-author attribution.

Official
Intermediate
mikersaysmikersays

issue-init

Initialize a structured issue tracking system in a Git repository.

Community
Intermediate
eveldeveld
10

before-file-search

Redirect exploratory file searches to the codebase-locator agent before using grep or glob.

Community
Basic