@therocketcode/gsd-core 1.5.0 → 1.6.1

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "gsd-core",
   "displayName": "GSD Core",
-  "version": "1.5.0",
+  "version": "1.6.1",
   "description": "GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.",
   "author": {
     "name": "TheRocketCodeMX",

package/agents/gsd-roadmapper.md

@@ -441,6 +441,10 @@ Orchestrator provides:
 - research/SUMMARY.md content (if exists - phase suggestions)
 - config.json (granularity setting)
 
+**Also read these project-level discovery artifacts if they exist** (e.g. on a new milestone, or when discovery was run before the roadmap):
+- `.planning/DOMAIN-MODEL.md` — group phases so each delivers a coherent subdomain capability; keep core-subdomain work cohesive rather than scattered across unrelated phases.
+- the latest `.planning/adr/*.md` — let the architecture topology inform phase dependencies (e.g. shared ports/adapters land before the features that use them).
+
 Parse and confirm understanding before proceeding.
 
 ## Step 2: Extract Requirements

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "gsd-core",
-  "version": "1.5.0",
+  "version": "1.6.1",
   "description": "GSD Core — a meta-prompting, context engineering, and spec-driven development system for AI coding agents. Loads gsd's operating context into every Gemini CLI session.",
   "contextFileName": "GEMINI.md"
 }

package/gsd-core/workflows/add-tests.md

@@ -70,6 +70,8 @@ Present banner:
 <step name="analyze_implementation">
 Extract the list of files modified by the phase from SUMMARY.md ("Files Changed" or equivalent section).
 
+**If `.planning/TEST-STRATEGY.md` exists, read it first and let it drive classification** — map each changed file to its subdomain and use the strategy's per-subdomain test level (unit → TDD; integration → TDD-style but exercised against real dependencies; e2e → E2E) plus its gnarly-bits and what-not-to-test lists, instead of the generic heuristics below. When the strategy prescribes integration/e2e for a file, pull the test-infra references it links (`@~/.claude/gsd-core/references/test-containers.md`, `db-test-isolation.md`, `auth-in-tests.md`, `realistic-test-data.md`, `flaky-test-checklist.md`) into the generated test's setup. Use the heuristics below only for files the strategy doesn't cover.
+
 For each file, classify into one of three categories:
 
 | Category | Criteria | Test Type |

package/gsd-core/workflows/discuss-phase.md

@@ -293,6 +293,7 @@ Analyze the phase to identify gray areas. Use both `prior_decisions` and `codeba
 
 1b. **Initialize canonical refs accumulator** — Start building `<canonical_refs>` for CONTEXT.md. Sources:
    - **Now:** Copy `Canonical refs:` from ROADMAP.md for this phase. Expand each to a full relative path. Check REQUIREMENTS.md and PROJECT.md for specs/ADRs referenced.
+   - **Project discovery artifacts (if present):** add `.planning/DOMAIN-MODEL.md` (ubiquitous language + core/supporting/generic subdomains), the most recent `.planning/adr/*.md` (the architecture decision — per-subdomain domain-logic rung + topology), and `.planning/TEST-STRATEGY.md` (per-subdomain test levels + the linked test-infra how-to references). These are project-wide and apply to EVERY phase: planning and implementation MUST follow the domain model, the architecture decision, and the test strategy. For each, note its role (e.g. "Architecture decision — MUST follow the chosen rung per subdomain"). When `TEST-STRATEGY.md` is present, the plan's test tasks must also pull in the specific `gsd-core/references/<test-infra>.md` it links for the level being written.
    - **`scout_codebase`:** If existing code references docs (e.g., comments citing ADRs), add those.
    - **`discuss_areas`:** When the user says "read X", "check Y", or references any doc/spec/ADR — add it immediately. These are often the MOST important refs.
 

package/gsd-core/workflows/plan-phase.md

@@ -831,6 +831,7 @@ Pattern mapper prompt:
 
 <files_to_read>
 - {context_path} (USER DECISIONS from /gsd:discuss-phase)
+- **Every file listed under `## Canonical References` inside {context_path}** — these are MANDATORY ("Downstream agents MUST read these before planning"). When they include a DOMAIN-MODEL.md, an architecture ADR, or a TEST-STRATEGY.md, the plan MUST follow the domain model's subdomain classification, the architecture decision's per-subdomain rung, and the test strategy's per-subdomain test levels — and pull the test-infra references that TEST-STRATEGY links into the `@`-context of the relevant test tasks. Also read `.planning/DOMAIN-MODEL.md`, the latest `.planning/adr/*.md`, and `.planning/TEST-STRATEGY.md` directly if they exist — they are project-wide and always apply, even when not listed.
 - {research_path} (Technical Research)
 </files_to_read>
 
@@ -895,6 +896,7 @@ Planner prompt:
 - {roadmap_path} (Roadmap)
 - {requirements_path} (Requirements)
 - {context_path} (USER DECISIONS from /gsd:discuss-phase)
+- **Every file listed under `## Canonical References` inside {context_path}** — these are MANDATORY ("Downstream agents MUST read these before planning"). When they include a DOMAIN-MODEL.md, an architecture ADR, or a TEST-STRATEGY.md, the plan MUST follow the domain model's subdomain classification, the architecture decision's per-subdomain rung, and the test strategy's per-subdomain test levels — and pull the test-infra references that TEST-STRATEGY links into the `@`-context of the relevant test tasks. Also read `.planning/DOMAIN-MODEL.md`, the latest `.planning/adr/*.md`, and `.planning/TEST-STRATEGY.md` directly if they exist — they are project-wide and always apply, even when not listed.
 - {research_path} (Technical Research)
 - {PATTERNS_PATH} (Pattern Map — analog files and code excerpts, if exists)
 - {verification_path} (Verification Gaps - if --gaps)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@therocketcode/gsd-core",
-  "version": "1.5.0",
+  "version": "1.6.1",
   "description": "GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.",
   "bin": {
     "gsd-core": "bin/install.js",