Skip to content
Back to skills

Brainstorming Exploring

ASecurity

The EXPLORING phase gathers context about the project and forms an initial understanding

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
code-qualitybashgitdocumentation

Works with

  • mcp

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill brainstorming-exploring --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Brainstorming Exploring?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Brainstorming Exploring
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-brainstorming-exploring/badge)](https://www.skillsdirectory.com/skills/david-li0406-brainstorming-exploring)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: brainstorming-exploring
description: The EXPLORING phase gathers context about the project and forms an initial understanding
user-invocable: false
allowed-tools:
  - Read
  - Glob
  - Grep
  - Bash
  - AskUserQuestion
  - mcp__plugin_mermaid-collab_mermaid__*
---

# EXPLORING Phase

The EXPLORING phase gathers context about the project and forms an initial understanding of what needs to be built.

## Purpose

- Understand the current project state
- Read relevant files and documentation
- Check recent git history for context
- Form an initial list of items/topics to discuss

## Process

1. **Check project state:**
   - Read relevant files (code, docs, configs)
   - Check recent commits for context
   - Understand existing architecture

2. **Gather requirements context:**
   - Review any existing specs or requirements
   - Understand stakeholder expectations
   - Identify constraints and dependencies

3. **Form initial item list:**
   - Create a preliminary list of topics to discuss
   - Group related items together
   - Prioritize by importance/dependencies

## Single-Item Mode (EXPLORING)

When `currentItem` is set in collab-state.json:

- Read relevant files based on item description
- Check git history for related changes
- Gather context specific to this item only
- Do NOT expand scope beyond this item

## Exit Criteria

- Context gathered from relevant files
- Initial list of items/topics formed
- Ready to discuss items one at a time

## Checkpoint: Current State Diagram

**REQUIRED** before proceeding to CLARIFYING:

Create a diagram showing the current state relevant to this work:

```
Tool: mcp__mermaid__create_diagram
Args: {
  "project": "<cwd>",
  "session": "<session>",
  "name": "current-state-item-N",
  "content": <flowchart showing existing components/flow>
}
```

Display: "Current state diagram: [previewUrl]"

If the work item doesn't involve architecture/flow (e.g., pure text changes), create a simple diagram showing the file(s) being modified:

```mermaid
graph LR
    A[File: path/to/file.md] --> B[Section being modified]
```

## Transition to CLARIFYING

**Prerequisites:**
- Read relevant files/context
- Formed initial list of items

**Announce:** "I've gathered context. Now let me discuss each item with you one at a time."

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…