gsd-cc 1.1.2 → 1.1.3
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/package.json +1 -1
- package/skills/gsd/ingest/SKILL.md +26 -6
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "gsd-cc",
|
|
3
|
-
"version": "1.1.
|
|
3
|
+
"version": "1.1.3",
|
|
4
4
|
"description": "Get Shit Done on Claude Code — structured AI development with your Max plan",
|
|
5
5
|
"author": "Philipp Briese (https://github.com/0ui-labs)",
|
|
6
6
|
"homepage": "https://github.com/0ui-labs/GSD-CC#readme",
|
|
@@ -41,17 +41,37 @@ Read the entire document. Then explain IN YOUR OWN WORDS what you understood —
|
|
|
41
41
|
```
|
|
42
42
|
OK, I've read through everything. Let me tell you what I understood —
|
|
43
43
|
correct me wherever I'm wrong.
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
Then explain in your own words, structured into clear sections:
|
|
47
|
+
|
|
48
|
+
```
|
|
49
|
+
THE PROBLEM
|
|
50
|
+
{What pain point or need does this address? Why does this project
|
|
51
|
+
exist? What's the current situation that's not good enough?}
|
|
52
|
+
|
|
53
|
+
THE SOLUTION
|
|
54
|
+
{What are we building? One paragraph, plain language, no jargon.}
|
|
55
|
+
|
|
56
|
+
WHO IT'S FOR
|
|
57
|
+
{Who uses this? What's their situation? What do they care about?}
|
|
58
|
+
|
|
59
|
+
HOW IT WORKS
|
|
60
|
+
{The core workflow or experience — what happens step by step when
|
|
61
|
+
someone uses it? Walk through the main journey.}
|
|
62
|
+
|
|
63
|
+
HOW IT LOOKS & FEELS
|
|
64
|
+
{Design direction, vibe, personality — if the document mentions this.
|
|
65
|
+
Skip if the document is purely technical.}
|
|
44
66
|
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
- How it works at a high level
|
|
49
|
-
- What makes it different or interesting}
|
|
67
|
+
WHAT MAKES IT DIFFERENT
|
|
68
|
+
{Why not use an existing solution? What's the unique angle?
|
|
69
|
+
Skip if not apparent from the document.}
|
|
50
70
|
|
|
51
71
|
Did I get that right, or did I misunderstand something?
|
|
52
72
|
```
|
|
53
73
|
|
|
54
|
-
**This is the most important step.** Write it like you're explaining the project to someone new. Use simple language. Don't parrot the document back — rephrase it to show you actually understood the intent.
|
|
74
|
+
**This is the most important step.** Write it like you're explaining the project to someone new. Use simple language. Don't parrot the document back — rephrase it to show you actually understood the intent. Not every section needs to be long — if the document doesn't cover "how it looks", write one sentence or skip it. But the structure helps the user quickly spot where you got it wrong.
|
|
55
75
|
|
|
56
76
|
**Wait for the user's response.** They might say:
|
|
57
77
|
- "Yes, exactly!" → proceed to Step 3
|