@ggdna/dna-gg 0.2.0 → 0.3.0

package/README.md

@@ -14,6 +14,13 @@ publish.
   `dna/doc/guides/install-guide/install-gg-workspace-guide.md` — install
   `gg` and set up a workspace
 
+## CLAUDE.md
+
+- `dna/CLAUDE.md` — points the agent to the `ai-dev-guide` and the
+  skills. helix writes it into the managed block of the consumer's
+  `CLAUDE.md` (`<!-- helix:claude_md:start/end -->`), everything outside
+  the block stays with the repo.
+
 ## Skills
 
 - `/ticket` — creates a ticket and adds the repos it needs

package/dna/CLAUDE.md

@@ -0,0 +1,10 @@
+# gg workflow
+
+This repo is developed ticket by ticket with the `gg` CLI. Follow the
+development guide, it tells you when to ask the user and which command
+comes next:
+
+@doc/guides/for-ai/ai-dev-guide.md
+
+The steps are also available as skills: `/ticket`, `/commit`, `/push`,
+`/publish`, `/cleanup`.

package/dna/_generated.json

@@ -5,9 +5,9 @@
       "name": "base",
       "package": "helix",
       "ecosystem": null,
-      "resolvedVersion": "1.3.1",
+      "resolvedVersion": "1.6.1",
       "via": null,
-      "hash": "0x705e486e88a93125"
+      "hash": "0x6883da335b415f9d"
     },
     {
       "name": "dna-install",
@@ -31,14 +31,15 @@
       "ecosystem": null,
       "resolvedVersion": null,
       "via": null,
-      "hash": "0x97c559b0151610d4"
+      "hash": "0x9f13019b84e4b029"
     }
   ],
   "claude": {
-    "claudeMdInclude": null
+    "claudeMdInclude": null,
+    "claudeMdFromDna": true
   },
-  "baseVersion": "1.3.1",
-  "baseHash": "0x705e486e88a93125",
+  "baseVersion": "1.6.1",
+  "baseHash": "0x6883da335b415f9d",
   "instances": [
     {
       "path": ".claude/skills/cleanup/SKILL.md",
@@ -66,7 +67,7 @@
     },
     {
       "path": ".claude/skills/ticket/SKILL.md",
-      "hash": "0xbc13efe6fa9af962"
+      "hash": "0xa86135ff5b7f5ddf"
     },
     {
       "path": ".github/workflows/quick_check.yaml",
@@ -82,7 +83,7 @@
     },
     {
       "path": "doc/guides/for-ai/ai-dev-guide.md",
-      "hash": "0x3d2812a1dfb025cf"
+      "hash": "0x34d8b0200c0d657b"
     },
     {
       "path": "doc/guides/index-guide.md",
@@ -118,7 +119,7 @@
     },
     {
       "path": "doc/guides/install-guide/install-gg-workspace-guide.md",
-      "hash": "0x846766914bb56a84"
+      "hash": "0xc06dc45d20e1bf79"
     },
     {
       "path": "doc/guides/install-guide/install-github-cli-guide.md",
@@ -136,10 +137,6 @@
       "path": "doc/guides/install-guide/install-vscode-guide.md",
       "hash": "0xa0da6a6877bb94c2"
     },
-    {
-      "path": "doc/hello_world.md",
-      "hash": "0x0903f7fc5224f6f1"
-    },
     {
       "path": "doc/templates/index-template.jsonc",
       "hash": "0x16c3a8d50c72ed6d"

package/dna/doc/guides/for-ai/ai-dev-guide.md

@@ -29,6 +29,23 @@ gg do create ticket dnaJiraPrefix-145 -m"Fix issue abc"
 cd tickets/dnaJiraPrefix-145
 ```
 
+## Choose the project management repo
+
+Every ticket belongs to a project management (PM) repo. It holds the plans,
+decisions and blog posts of a project, but no code.
+
+Look at the `index.jsonc` of each repo in .ocean and find the PM repo the
+ticket belongs to: its summary or domain talks about project management or
+planning, not about code. If one fits, propose it to the user. If none fits,
+ask the user which repo to use, or whether to create a new PM repo.
+
+After the user's confirmation, add the PM repo to the ticket **before** any
+other repo:
+
+```bash
+gg do add pm_repo
+```
+
 ## Add git repositories
 
 Look at the `index.jsonc` of each repo in .ocean and decide which repos need to
@@ -40,6 +57,9 @@ Ask the user about this. Also explain to the user what you roughly want to
 change in which repo to implement the ticket and let them confirm that the
 corresponding repos are added to the ticket.
 
+If the ticket is only planned (see below), the PM repo may be the only repo
+of the ticket.
+
 After the user's confirmation, add the repos to the ticket:
 
 ```bash
@@ -52,9 +72,23 @@ gg do add repo1 repo2
 gg do code
 ```
 
-## Implement
+## Plan (optional)
+
+Ask the user whether the ticket is planned before it is implemented.
+
+If yes, write the plan into the PM repo, following the guides of the PM repo:
+the goal, the affected repos, the rough steps and open questions. Let the user
+review the plan and revise it until they confirm it.
+
+## Implement (optional)
+
+Ask the user whether the ticket is implemented now, or whether it is only
+planned. Some tickets are only planned; the implementation follows in a later
+ticket.
 
-Implement your features based on the guides
+- Implement: implement your features based on the guides
+- Plan only: skip this step. The following steps then apply to the PM repo
+  only.
 
 ## Commit
 
@@ -86,6 +120,7 @@ Afterwards load the review-light skill and execute it.
 - Create a blog post for the current ticket
 - Update the index.jsonc and README.md
 - Create the configuration for gg do publish
+- If the ticket was only planned, publish the PM repo only
 
 Ask the user to run the following command **manually**:
 

package/dna/doc/guides/install-guide/install-gg-workspace-guide.md

@@ -21,6 +21,11 @@ cd ~/dev2
 gg do init workspace
 ```
 
+This creates the `.ocean` folder and instantiates the latest `dna_gg` in
+the workspace folder: the gg guides, the skills and the managed block of
+`CLAUDE.md`. It is the same as running `gg dna init`, `gg dna add dna_gg`
+and `gg dna build` by hand.
+
 ## Add your repositories
 
 ```bash

package/dna/dot-claude/skills/ticket/SKILL.md

@@ -21,12 +21,25 @@ gg do create ticket DnaJiraPrefix-145 -m"Fix issue abc"
 cd tickets/DnaJiraPrefix-145
 ```
 
-## 3. Choose the repos
+## 3. Choose the project management repo
+
+Every ticket belongs to a project management (PM) repo: plans, decisions and
+blog posts of a project, no code. Read the `index.md` of the repos in
+`.ocean` and propose the PM repo the ticket belongs to. If none fits, ask
+which repo to use or whether to create one.
+
+After the confirmation, add it **before** any other repo:
+
+```bash
+gg do add pm_repo
+```
+
+## 4. Choose the code repos
 
 Read the `index.md` of the candidate repos in `.ocean`. Tell the user which
 repos the ticket needs and what you roughly want to change in each one. If a
 part belongs to a domain that has no repo yet, say so and ask whether to
-create one.
+create one. A ticket that is only planned may need no code repo at all.
 
 After the confirmation:
 
@@ -34,12 +47,19 @@ After the confirmation:
 gg do add repo1 repo2
 ```
 
-## 4. Open the workspace
+## 5. Open the workspace
 
 ```bash
 gg do code
 ```
 
+## 6. Plan or implement
+
+Ask the user whether the ticket is planned first. If yes, write the plan into
+the PM repo and let the user confirm it. Then ask whether the ticket is
+implemented now or only planned — in the latter case the ticket ends with
+the PM repo alone.
+
 ## Important
 
 - Never add repos without confirmation. Rather too few than too many — more

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ggdna/dna-gg",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "DNA layer: gg CLI workflow guides, repo setup scripts and CI check",
   "keywords": [
     "dna",
@@ -32,7 +32,7 @@
     "@ggdna/dna-install": "^0.1.0"
   },
   "devDependencies": {
-    "@types/node": "^26.4.1",
+    "@types/node": "^26.5.0",
     "prettier": "^3.9.6"
   },
   "scripts": {