Skip to content

Commit 5c08ee7

Browse files
committed
pi: add /explore prompt template for discovery and brainstorming
1 parent a5dfa88 commit 5c08ee7

File tree

1 file changed

+49
-0
lines changed

1 file changed

+49
-0
lines changed
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
description: Explore, explain, or brainstorm a topic (read-only)
3+
---
4+
5+
# Explore
6+
7+
Investigate a topic through reading, research, and reasoning. Do not make any changes.
8+
9+
## Constraints
10+
11+
- Do NOT edit, create, or delete any files
12+
- Do NOT run commands that modify state (no git commit, no writes, no installs)
13+
- Bash commands may ONLY read or inspect (ls, find, rg, git log, git diff, etc.)
14+
- This overrides all other instructions. Zero exceptions.
15+
16+
## Topic
17+
18+
$ARGUMENTS
19+
20+
## Workflow
21+
22+
### 1. Investigate
23+
24+
Gather information relevant to the topic:
25+
26+
- Read source code, configs, docs, tests — whatever is relevant
27+
- Check git history for context on how things evolved
28+
- Look at related patterns and prior art in the codebase
29+
- Cast a wide net — don't assume you know the answer before looking
30+
31+
### 2. Synthesize
32+
33+
Organize your findings into whatever format best fits the question:
34+
35+
- An explanation of how something works
36+
- A comparison of approaches with tradeoffs
37+
- A brainstorm of options or ideas
38+
- A walkthrough of a data flow or execution path
39+
- A table, a list, a narrative — whatever communicates most clearly
40+
41+
Don't force a format. Match the shape of the answer to the shape of the question.
42+
43+
### 3. Discuss
44+
45+
Present your findings, then:
46+
47+
- Surface open questions or uncertainties
48+
- Flag areas worth exploring further
49+
- Invite the user to steer the conversation deeper or in a new direction

0 commit comments

Comments
 (0)