@ggdna/dna-gg 0.11.0 → 0.12.0
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/dna/_generated.json
CHANGED
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
"name": "base",
|
|
6
6
|
"package": "helix",
|
|
7
7
|
"ecosystem": null,
|
|
8
|
-
"resolvedVersion": "1.
|
|
8
|
+
"resolvedVersion": "1.13.0",
|
|
9
9
|
"via": null,
|
|
10
10
|
"hash": "0x6883da335b415f9d"
|
|
11
11
|
},
|
|
@@ -29,9 +29,9 @@
|
|
|
29
29
|
"name": "dna-github",
|
|
30
30
|
"package": "@ggdna/dna-github",
|
|
31
31
|
"ecosystem": "node",
|
|
32
|
-
"resolvedVersion": "0.1.
|
|
32
|
+
"resolvedVersion": "0.1.1",
|
|
33
33
|
"via": null,
|
|
34
|
-
"hash": "
|
|
34
|
+
"hash": "0xf541b93b3dc7995d"
|
|
35
35
|
},
|
|
36
36
|
{
|
|
37
37
|
"name": "self",
|
|
@@ -39,14 +39,14 @@
|
|
|
39
39
|
"ecosystem": null,
|
|
40
40
|
"resolvedVersion": null,
|
|
41
41
|
"via": null,
|
|
42
|
-
"hash": "
|
|
42
|
+
"hash": "0x80b4e958c7ac9afb"
|
|
43
43
|
}
|
|
44
44
|
],
|
|
45
45
|
"claude": {
|
|
46
46
|
"claudeMdInclude": null,
|
|
47
47
|
"claudeMdFromDna": true
|
|
48
48
|
},
|
|
49
|
-
"baseVersion": "1.
|
|
49
|
+
"baseVersion": "1.13.0",
|
|
50
50
|
"baseHash": "0x6883da335b415f9d",
|
|
51
51
|
"instances": [
|
|
52
52
|
{
|
|
@@ -71,7 +71,7 @@
|
|
|
71
71
|
},
|
|
72
72
|
{
|
|
73
73
|
"path": ".claude/skills/gg-ticket/SKILL.md",
|
|
74
|
-
"hash": "
|
|
74
|
+
"hash": "0xa238364995ac50f8"
|
|
75
75
|
},
|
|
76
76
|
{
|
|
77
77
|
"path": ".claude/skills/gg/SKILL.md",
|
|
@@ -99,7 +99,7 @@
|
|
|
99
99
|
},
|
|
100
100
|
{
|
|
101
101
|
"path": "doc/guides/for-ai/ai-dev-guide.md",
|
|
102
|
-
"hash": "
|
|
102
|
+
"hash": "0xb4ae698a82bc9e2c"
|
|
103
103
|
},
|
|
104
104
|
{
|
|
105
105
|
"path": "doc/guides/index-guide.md",
|
|
@@ -154,12 +154,12 @@
|
|
|
154
154
|
"hash": "0xa0da6a6877bb94c2"
|
|
155
155
|
},
|
|
156
156
|
{
|
|
157
|
-
"path": "doc/
|
|
158
|
-
"hash": "
|
|
157
|
+
"path": "doc/guides/setup-github-guide.md",
|
|
158
|
+
"hash": "0x836d4ca942a58b9c"
|
|
159
159
|
},
|
|
160
160
|
{
|
|
161
|
-
"path": "
|
|
162
|
-
"hash": "
|
|
161
|
+
"path": "doc/templates/index-template.jsonc",
|
|
162
|
+
"hash": "0x16c3a8d50c72ed6d"
|
|
163
163
|
},
|
|
164
164
|
{
|
|
165
165
|
"path": "scripts/setup-github-repo.js",
|
|
@@ -96,13 +96,20 @@ gg do code
|
|
|
96
96
|
|
|
97
97
|
## Plan (optional)
|
|
98
98
|
|
|
99
|
+
Requirements come before the plan. If the project management repo keeps
|
|
100
|
+
requirements (`doc/requirements`) and none of its accepted requirements
|
|
101
|
+
covers the ticket, engineer them with the user first — with
|
|
102
|
+
`/plan-requirements` if the repo has it — and plan the ticket only after
|
|
103
|
+
that. Bug tickets are the exception, they name their bug file.
|
|
104
|
+
|
|
99
105
|
Ask the user whether the ticket is planned before it is implemented.
|
|
100
106
|
|
|
101
107
|
If yes, write the plan into the project management repo, following its
|
|
102
108
|
`doc/guides/pm-repo-guide.md` if present, otherwise its other guides: the
|
|
103
|
-
goal, the affected repos, the rough steps and
|
|
104
|
-
project management repo, put the plan into the
|
|
105
|
-
review the plan and revise it until they confirm
|
|
109
|
+
goal, the requirements it fulfils, the affected repos, the rough steps and
|
|
110
|
+
open questions. Without a project management repo, put the plan into the
|
|
111
|
+
ticket itself. Let the user review the plan and revise it until they confirm
|
|
112
|
+
it.
|
|
106
113
|
|
|
107
114
|
## Implement (optional)
|
|
108
115
|
|
|
@@ -80,6 +80,11 @@ gg do code
|
|
|
80
80
|
|
|
81
81
|
## 6. Plan or implement
|
|
82
82
|
|
|
83
|
+
If the project management repo keeps requirements (`doc/requirements`)
|
|
84
|
+
and no accepted requirement covers the ticket, engineer them with the user
|
|
85
|
+
first — with `/plan-requirements` if the repo has it — before any plan or
|
|
86
|
+
code. Bug tickets are the exception, they name their bug file.
|
|
87
|
+
|
|
83
88
|
Ask the user whether the ticket is planned first. If yes, write the plan
|
|
84
89
|
into the project management repo as its `pm-repo-guide.md` describes (or as
|
|
85
90
|
its other guides do) and let the user confirm it. Without a project
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ggdna/dna-gg",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.12.0",
|
|
4
4
|
"description": "DNA layer: gg CLI workflow guides, repo setup scripts and CI check",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"dna",
|
|
@@ -28,7 +28,7 @@
|
|
|
28
28
|
"access": "public"
|
|
29
29
|
},
|
|
30
30
|
"dependencies": {
|
|
31
|
-
"@ggdna/dna-github": "^0.1.
|
|
31
|
+
"@ggdna/dna-github": "^0.1.1",
|
|
32
32
|
"@ggdna/dna-index": "^0.2.0",
|
|
33
33
|
"@ggdna/dna-install": "^0.2.0"
|
|
34
34
|
},
|