ateschh-kit 1.2.0 → 1.2.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/commands/brainstorm.md +18 -4
- package/.claude/settings.local.json +2 -1
- package/CHANGELOG.md +16 -0
- package/bin/install.js +0 -3
- package/package.json +1 -1
|
@@ -19,13 +19,27 @@ After `/new-project`, when you have an idea and want to analyze it properly befo
|
|
|
19
19
|
|
|
20
20
|
Read `projects/{name}/STATE.md` to confirm we're in Phase 1.
|
|
21
21
|
|
|
22
|
-
### Step 2:
|
|
22
|
+
### Step 2: Gather User Input
|
|
23
23
|
|
|
24
|
-
|
|
24
|
+
Ask the user to describe their idea in their own words — no structure required, just whatever is on their mind.
|
|
25
|
+
|
|
26
|
+
After reading the response, identify 3–5 follow-up questions that are **specific to this idea**. Choose questions that close the most important gaps in understanding. Examples of what to probe (pick what's relevant, don't ask all):
|
|
27
|
+
|
|
28
|
+
- Who is the primary user and what pain do they have today?
|
|
29
|
+
- What geography or market segment is the pilot targeting?
|
|
30
|
+
- Is there a business model in mind (B2B, B2C, marketplace, SaaS)?
|
|
31
|
+
- Are there any hard constraints (budget, timeline, regulation, existing tech)?
|
|
32
|
+
- What does "success in 6 months" look like?
|
|
33
|
+
- Has this been tried before — what happened?
|
|
34
|
+
|
|
35
|
+
Ask all chosen questions in a **single message** (numbered list). Wait for the user's answers before proceeding.
|
|
36
|
+
|
|
37
|
+
### Step 3: Spawn Idea Analyst Agent
|
|
38
|
+
|
|
39
|
+
Read `agents/idea-analyst.md` and spawn the agent with the user's idea **and their answers from Step 2**.
|
|
25
40
|
|
|
26
41
|
The idea-analyst uses the `idea-analysis` skill:
|
|
27
|
-
-
|
|
28
|
-
- Goal: understand the problem, target user, core value, and what success looks like
|
|
42
|
+
- Analyzes the problem, target user, core value, and success criteria
|
|
29
43
|
- Output: structured idea summary
|
|
30
44
|
|
|
31
45
|
Report findings to the user. Ask for confirmation before proceeding.
|
|
@@ -10,7 +10,8 @@
|
|
|
10
10
|
"WebFetch(domain:api.github.com)",
|
|
11
11
|
"Bash(mkdir -p /c/GENERATOR/.claude/commands)",
|
|
12
12
|
"Bash(mv /c/GENERATOR/workflows/*.md /c/GENERATOR/.claude/commands/)",
|
|
13
|
-
"WebFetch(domain:github.com)"
|
|
13
|
+
"WebFetch(domain:github.com)",
|
|
14
|
+
"Bash(git push:*)"
|
|
14
15
|
]
|
|
15
16
|
}
|
|
16
17
|
}
|
package/CHANGELOG.md
CHANGED
|
@@ -67,6 +67,22 @@ Format: [Semantic Versioning](https://semver.org/)
|
|
|
67
67
|
|
|
68
68
|
---
|
|
69
69
|
|
|
70
|
+
## [1.2.2] — 2026-04-06
|
|
71
|
+
|
|
72
|
+
### Changed
|
|
73
|
+
|
|
74
|
+
- `/brainstorm` now gathers user input dynamically before analysis — asks idea description first, then selects 3–5 context-specific follow-up questions
|
|
75
|
+
|
|
76
|
+
---
|
|
77
|
+
|
|
78
|
+
## [1.2.1] — 2026-04-06
|
|
79
|
+
|
|
80
|
+
### Fixed
|
|
81
|
+
|
|
82
|
+
- `bin/install.js` no longer attempts to copy the removed `workflows/` directory
|
|
83
|
+
|
|
84
|
+
---
|
|
85
|
+
|
|
70
86
|
## [1.2.0] — 2026-04-06
|
|
71
87
|
|
|
72
88
|
### Changed
|
package/bin/install.js
CHANGED
|
@@ -71,9 +71,6 @@ async function main() {
|
|
|
71
71
|
info('Copying .claude/rules/ ...')
|
|
72
72
|
copyDir(path.join(kitDir, '.claude'), path.join(targetDir, '.claude'))
|
|
73
73
|
|
|
74
|
-
info('Copying workflows/ ...')
|
|
75
|
-
copyDir(path.join(kitDir, 'workflows'), path.join(targetDir, 'workflows'))
|
|
76
|
-
|
|
77
74
|
info('Copying agents/ ...')
|
|
78
75
|
copyDir(path.join(kitDir, 'agents'), path.join(targetDir, 'agents'))
|
|
79
76
|
|