need-explorer

Name: need-explorer
Author: MageByte-Zero

24installs58forks

How to install need-explorer?

magebyte-zero/spec-superflow/need-explorer

$npx -y skills add MageByte-Zero/spec-superflow --skill need-explorer

Installs into the current project.

Summary

Clarify intent, scope, constraints, and success criteria before artifact creation. Invoke when the request is fuzzy, the user is comparing options, or the workflow needs a stable change definition before writing artifacts.

Files · 1

View on GitHub

SKILL.md

1	# Need Explorer
2
3	Turn a rough idea into a stable change definition before writing artifacts.
4
5	## Primary Goal
6
7	Agree on: problem, scope, non-goals, success criteria, whether to split before specification.
8
9	## Process
10
11	### 1. Inspect Context First
12
13	Before asking questions, understand what exists and what constraints are in place.
14
15	### 2. One Question at a Time
16
17	Ask a single clear question, wait for the answer, digest, then ask the next. Never ask 3+ questions at once. Each answer informs the next question.
18
19	### 3. Prefer Multiple-Choice Questions
20
21	Present 2-3 options when reasonable answers are finite. This reduces cognitive load and surfaces unconsidered choices.
22
23	### 4. Propose 2-3 Approaches with Trade-Offs
24
25	For each approach: what it is, upside, downside, best-for. Then recommend one and explain why. Never present a single path — always name at least one alternative.
26
27	### 5. Validate Before Concluding
28
29	Restate what you heard: "Here's what I'm hearing: [problem, scope, non-goals, success criteria]. Does this match?" Incorporate corrections and re-validate.
30
31	### 6. DP-1: Requirement Confirmation Gate
32
33	After user confirms the summary:
34	```bash
35	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_1_result "confirmed: <one-line summary>"
36	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_1_timestamp $(date -u +%Y-%m-%dT%H:%M:%SZ)
37	```
38	DP-1 confirms scope, non-goals, and success criteria before artifact creation.
39
40	### 7. Hand Off
41
42	Once DP-1 is recorded, hand off to `spec-writer`.
43
44	## Anti-Patterns
45
46	- Skipping exploration: "Simple" changes have scope too. Five minutes of exploration prevents two hours of rework.
47	- Proposing solutions before clarifying: If the user says "add caching," first ask what problem caching solves.
48	- Exploring indefinitely: Stop when change name, problem statement, scope, non-goals, success criteria, and decomposition decision are all clear.
49
50	## Exploration Standard
51
52	You must leave exploration with: a usable change name, a crisp problem statement, scope boundaries, non-goals, success criteria, and a decomposition decision (one change or split).
53
54	## Strong Rule
55
56	Do not produce implementation code. This skill stabilizes intent, not builds.
57
58	## Self-Review Before Handoff
59
60	1. Placeholder scan: No "probably", "maybe", "TBD", or "we'll figure it out later"
61	2. Contradiction check: No scope items conflicting with non-goals or constraints
62	3. Scope check: Can a developer draw a bright line between in and out?
63
64	## Exception Handling
65
66	- Parse failures: Report the specific file, proceed with available information
67	- Missing files: Note absent essential files as constraints, continue
68	- User interruption: Exploration is stateless — on resume, re-ask the current question

People who liked this also viewed

6 picks

Type

need-explorer

24installs58forks

View on GitHub

How to install need-explorer?

magebyte-zero/spec-superflow/need-explorer

$npx -y skills add MageByte-Zero/spec-superflow --skill need-explorer

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Need Explorer
2
3	Turn a rough idea into a stable change definition before writing artifacts.
4
5	## Primary Goal
6
7	Agree on: problem, scope, non-goals, success criteria, whether to split before specification.
8
9	## Process
10
11	### 1. Inspect Context First
12
13	Before asking questions, understand what exists and what constraints are in place.
14
15	### 2. One Question at a Time
16
17	Ask a single clear question, wait for the answer, digest, then ask the next. Never ask 3+ questions at once. Each answer informs the next question.
18
19	### 3. Prefer Multiple-Choice Questions
20
21	Present 2-3 options when reasonable answers are finite. This reduces cognitive load and surfaces unconsidered choices.
22
23	### 4. Propose 2-3 Approaches with Trade-Offs
24
25	For each approach: what it is, upside, downside, best-for. Then recommend one and explain why. Never present a single path — always name at least one alternative.
26
27	### 5. Validate Before Concluding
28
29	Restate what you heard: "Here's what I'm hearing: [problem, scope, non-goals, success criteria]. Does this match?" Incorporate corrections and re-validate.
30
31	### 6. DP-1: Requirement Confirmation Gate
32
33	After user confirms the summary:
34	```bash
35	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_1_result "confirmed: <one-line summary>"
36	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_1_timestamp $(date -u +%Y-%m-%dT%H:%M:%SZ)
37	```
38	DP-1 confirms scope, non-goals, and success criteria before artifact creation.
39
40	### 7. Hand Off
41
42	Once DP-1 is recorded, hand off to `spec-writer`.
43
44	## Anti-Patterns
45
46	- Skipping exploration: "Simple" changes have scope too. Five minutes of exploration prevents two hours of rework.
47	- Proposing solutions before clarifying: If the user says "add caching," first ask what problem caching solves.
48	- Exploring indefinitely: Stop when change name, problem statement, scope, non-goals, success criteria, and decomposition decision are all clear.
49
50	## Exploration Standard
51
52	You must leave exploration with: a usable change name, a crisp problem statement, scope boundaries, non-goals, success criteria, and a decomposition decision (one change or split).
53
54	## Strong Rule
55
56	Do not produce implementation code. This skill stabilizes intent, not builds.
57
58	## Self-Review Before Handoff
59
60	1. Placeholder scan: No "probably", "maybe", "TBD", or "we'll figure it out later"
61	2. Contradiction check: No scope items conflicting with non-goals or constraints
62	3. Scope check: Can a developer draw a bright line between in and out?
63
64	## Exception Handling
65
66	- Parse failures: Report the specific file, proceed with available information
67	- Missing files: Note absent essential files as constraints, continue
68	- User interruption: Exploration is stateless — on resume, re-ask the current question

People who liked this also viewed

6 picks

Type