@ggdna/dna-gg 1.4.1 → 1.5.1

package/README.md

@@ -51,10 +51,12 @@ All skills of this layer are prefixed with `gg-`:
   Claude Code in the project management repo `dnaPmRepo` names. The
   prompts wait in `~/.claude/pm-prompts/sessions/` and are committed to the
   branch `prompts` of that repo when a session starts or ends, under
-  `doc/prompts/<first name>/<yyyy-mm>/<yyyy-mm-dd>_<repo>_<session>.md`.
-  The first name comes from `doc/team/people.md` there, found by the git
+  `doc/<yyyy>-Q<n>/prompts/<first name>/<yyyy-mm-dd>_<repo>_<session>.md`,
+  the quarter of the day the session started. The first name comes from
+  `team/people.md` of the newest quarter folder there (`doc/team/people.md`
+  in a repo without quarter folders), found by the git
   user name: a first name equal to it or to its first word, or a `Git`
-  line listing it. An unknown name goes to `doc/prompts/_unknown/`. No
+  line listing it. An unknown name goes to `prompts/_unknown/`. No
   e-mail address is read or written; the commits carry the neutral author
   `pm-prompts`. Only the prompts are kept, never the answers; tokens and
   passwords are replaced by `[redacted]`. No working tree is touched: the commit is built in a bare

package/dna/_generated.json

@@ -39,7 +39,7 @@
       "ecosystem": null,
       "resolvedVersion": null,
       "via": null,
-      "hash": "0x958d0143021b2328"
+      "hash": "0x47e288578bf3e862"
     }
   ],
   "claude": {
@@ -59,7 +59,7 @@
     },
     {
       "path": ".claude/hooks/pm-prompts.mjs",
-      "hash": "0xf4266eea17b3b9c1"
+      "hash": "0x6b8fdf7bbbf7c1a5"
     },
     {
       "path": ".claude/settings.json",
@@ -75,7 +75,7 @@
     },
     {
       "path": ".claude/skills/gg-publish/SKILL.md",
-      "hash": "0xcdef2684fcaaac5a"
+      "hash": "0x806b4c1fd5f6f654"
     },
     {
       "path": ".claude/skills/gg-push/SKILL.md",
@@ -87,7 +87,7 @@
     },
     {
       "path": ".claude/skills/gg-ticket/SKILL.md",
-      "hash": "0xb1095b91b3531897"
+      "hash": "0xa44f6e5ad54a6d0b"
     },
     {
       "path": ".claude/skills/gg/SKILL.md",
@@ -107,15 +107,15 @@
     },
     {
       "path": "doc/guides/develop-guide.md",
-      "hash": "0xed4328d138fe76ef"
+      "hash": "0x4c378a55b3c4773b"
     },
     {
       "path": "doc/guides/develop-without-ai-guide.md",
-      "hash": "0xe74449f72357f23c"
+      "hash": "0xc0d6546a678cb8cc"
     },
     {
       "path": "doc/guides/for-ai/ai-dev-guide.md",
-      "hash": "0xe8182903f11a1766"
+      "hash": "0x3f2e79da5752c5fe"
     },
     {
       "path": "doc/guides/index-guide.md",

package/dna/doc/guides/develop-guide.md

@@ -45,10 +45,12 @@ Use the following skills in Claude
 ## Your prompts
 
 When the repo belongs to a project management repo, every prompt you write
-to Claude Code is kept there, under `doc/prompts/<your first name>/` on the
-branch `prompts`. Only the prompts, not the answers. Tokens and passwords
+to Claude Code is kept there, under
+`doc/<yyyy>-Q<n>/prompts/<your first name>/` on the branch `prompts`. Only the prompts, not the answers. Tokens and passwords
 are replaced by `[redacted]`. Your first name comes from
-`doc/team/people.md` in the project management repo: the person whose
+`team/people.md` of the newest quarter folder `doc/<yyyy>-Q<n>` in the
+project management repo: the person whose
 first name is your git user name or its first word, or whose `Git` line
 lists your git user name. Otherwise your prompts land in
-`doc/prompts/_unknown/`. Your e-mail address never goes there.
+`doc/<yyyy>-Q<n>/prompts/_unknown/`. Your e-mail address never goes
+there.

package/dna/doc/guides/develop-without-ai-guide.md

@@ -22,12 +22,15 @@ If you have not done that yet:
 cd ~/dev/
 ```
 
-## Add tickets
+## Add repos to the ticket
 
 ```bash
 gg do add repo1 repo2
 ```
 
+Name all repos in one call: every call refreshes the ocean and builds
+the dependency graph again.
+
 ## Open the workspace in Vscode
 
 ```bash

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

@@ -104,6 +104,12 @@ After the user's confirmation, add the repos to the ticket:
 gg do add repo1 repo2
 ```
 
+Name all code repos in this one call, never one `gg do add` per repo —
+not even for repos you find one after the other. Every call refreshes
+the ocean and builds the dependency graph again, and a ticket repo that
+depends on several new repos is resolved again for each call. The same
+goes for repos you find later, while implementing: add them together.
+
 ## Keep every repo in its scope
 
 Every repo covers one fixed scope: the `summary` and `domain` of its
@@ -121,7 +127,8 @@ as code does not fit the repo it is in or is about to land in:
   covers: propose creating one with `gg do create repo`, which adds it to
   the ticket
 - **Add an existing repo** — the code belongs to a repo in .ocean that is
-  not part of the ticket yet: propose adding it with `gg do add`
+  not part of the ticket yet: propose adding it with `gg do add`,
+  several repos in one call
 - **Move code** — existing code, or code you just wrote, belongs to another
   repo: propose moving it there
 
@@ -158,7 +165,8 @@ gg do code
 ## Plan (optional)
 
 Requirements come before the plan. If the project management repo keeps
-requirements (`doc/requirements`) and none of its accepted requirements
+requirements (`doc/<yyyy>-Q<n>/requirements`, in the newest quarter
+folder) and none of its accepted requirements
 covers the ticket, engineer them with the user first — with
 `/gg-plan-requirements` if the repo has it — and plan the ticket only after
 that. Bug tickets are the exception, they name their bug file.

package/dna/dot-claude/hooks/pm-prompts.mjs

@@ -17,8 +17,10 @@ import { fileURLToPath, pathToFileURL } from 'node:url';
 /** The branch of the project management repo holding the prompts. */
 export const promptsBranch = 'prompts';
 
-const promptsDir = 'doc/prompts';
-const peopleFile = 'doc/team/people.md';
+// Everything a project management repo plans lives in quarter folders
+// doc/<yyyy>-Q<n>; repos not moved yet keep doc/team.
+const quarterDir = /^doc\/(\d{4}-Q[1-4])$/;
+const legacyPeopleFile = 'doc/team/people.md';
 const configFile = path.join('.claude', 'hooks', 'pm-prompts.json');
 
 // A session that ended without an end event counts as ended after a week.
@@ -330,12 +332,32 @@ export function personOf(gitName, peopleMd) {
   );
 }
 
+/** The quarter folder name of a local date: 2026-11-06 → 2026-Q4. */
+export function quarterOf(date) {
+  const month = Number(date.slice(5, 7));
+  return `${date.slice(0, 4)}-Q${Math.floor((month - 1) / 3) + 1}`;
+}
+
 /** Where the prompts of a session go in the project management repo. */
 export function promptsPath(meta, person) {
   const date = localDate(meta.started);
   const folder = person ? slug(person) : '_unknown';
   const id = String(meta.session).slice(0, 8);
-  return `${promptsDir}/${folder}/${date.slice(0, 7)}/${date}_${slug(meta.folder) || 'session'}_${id}.md`;
+  const name = `${date}_${slug(meta.folder) || 'session'}_${id}.md`;
+  return `doc/${quarterOf(date)}/prompts/${folder}/${name}`;
+}
+
+/**
+ * The files people.md may be in, best first: the team of the newest quarter
+ * folder among the [entries] of doc, then the one of a repo not moved yet.
+ */
+export function peopleFiles(entries) {
+  const quarters = entries
+    .map((e) => quarterDir.exec(e.trim())?.[1])
+    .filter(Boolean)
+    .sort()
+    .reverse();
+  return [...quarters.map((q) => `doc/${q}/team/people.md`), legacyPeopleFile];
 }
 
 /** The head of the file a session's prompts start. */
@@ -392,7 +414,12 @@ function ensureCache(url) {
 function readPeople(dir) {
   const fetched = git(['-C', dir, 'fetch', '-q', '--depth=1', 'origin', 'HEAD']);
   if (!fetched.ok) throw new Error(`fetch HEAD: ${fetched.err}`);
-  return git(['-C', dir, 'show', `FETCH_HEAD:${peopleFile}`]).out;
+  const ls = git(['-C', dir, 'ls-tree', '--name-only', 'FETCH_HEAD', 'doc/']);
+  for (const file of peopleFiles(ls.ok ? ls.out.split('\n') : [])) {
+    const shown = git(['-C', dir, 'show', `FETCH_HEAD:${file}`]);
+    if (shown.ok) return shown.out;
+  }
+  return '';
 }
 
 // The tip of the prompts branch, '' while it does not exist yet.

package/dna/dot-claude/skills/gg-publish/SKILL.md

@@ -13,7 +13,8 @@ creates and pushes the version tags. It is interactive — the user runs it.
 - Every repo of the ticket is committed and pushed.
 - The pull requests created by `gg do review` are green.
 - Every repo with `doc/guides/blog-guide.md` holds the post of this ticket
-  in `doc/blog/<yyyy>`. If one is missing, go back to `/gg-review`.
+  in `doc/blog/<yyyy>`, a project management repo in
+  `doc/<yyyy>-Q<n>/blog`. If one is missing, go back to `/gg-review`.
 
 ## 2. Configure the publish
 

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

@@ -90,6 +90,12 @@ After the confirmation:
 gg do add repo1 repo2
 ```
 
+Name all code repos in this one call, never one `gg do add` per repo —
+not even for repos you find one after the other. Every call refreshes
+the ocean and builds the dependency graph again, and a ticket repo that
+depends on several new repos is resolved again for each call. The same
+goes for repos you find later, while implementing: add them together.
+
 ## 5. Open the workspace only on request
 
 Do not open VS Code on your own — many tickets need no editor. Tell the
@@ -103,8 +109,9 @@ Run it only when the user asks for it.
 
 ## 6. Plan or implement
 
-If the project management repo keeps requirements (`doc/requirements`)
-and no accepted requirement covers the ticket, engineer them with the user
+If the project management repo keeps requirements
+(`doc/<yyyy>-Q<n>/requirements`, in the newest quarter folder) and no
+accepted requirement covers the ticket, engineer them with the user
 first — with `/gg-plan-requirements` if the repo has it — before any plan or
 code. Bug tickets are the exception, they name their bug file.
 
@@ -135,7 +142,8 @@ not fit the repo it is in or is about to land in:
 
 - **Split a repo** that has grown a second scope into two repos
 - **Add a new repo** with `gg do create repo` for a domain no repo covers
-- **Add an existing repo** with `gg do add` when the code belongs there
+- **Add an existing repo** with `gg do add` when the code belongs there;
+  several repos in one call
 - **Move code**, existing or just written, into the repo whose scope it fits
 
 Name the code, the repo it is in, the repo it should go to and why. Let the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ggdna/dna-gg",
-  "version": "1.4.1",
+  "version": "1.5.1",
   "description": "DNA layer: gg CLI workflow guides, repo setup scripts and CI check",
   "keywords": [
     "dna",