@therocketcode/gsd-core 1.5.0 → 1.6.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.
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "gsd-core",
|
|
3
3
|
"displayName": "GSD Core",
|
|
4
|
-
"version": "1.
|
|
4
|
+
"version": "1.6.0",
|
|
5
5
|
"description": "GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "TheRocketCodeMX",
|
package/gemini-extension.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "gsd-core",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.6.0",
|
|
4
4
|
"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.",
|
|
5
5
|
"contextFileName": "GEMINI.md"
|
|
6
6
|
}
|
|
@@ -293,6 +293,7 @@ Analyze the phase to identify gray areas. Use both `prior_decisions` and `codeba
|
|
|
293
293
|
|
|
294
294
|
1b. **Initialize canonical refs accumulator** — Start building `<canonical_refs>` for CONTEXT.md. Sources:
|
|
295
295
|
- **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.
|
|
296
|
+
- **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.
|
|
296
297
|
- **`scout_codebase`:** If existing code references docs (e.g., comments citing ADRs), add those.
|
|
297
298
|
- **`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.
|
|
298
299
|
|
|
@@ -831,6 +831,7 @@ Pattern mapper prompt:
|
|
|
831
831
|
|
|
832
832
|
<files_to_read>
|
|
833
833
|
- {context_path} (USER DECISIONS from /gsd:discuss-phase)
|
|
834
|
+
- **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.
|
|
834
835
|
- {research_path} (Technical Research)
|
|
835
836
|
</files_to_read>
|
|
836
837
|
|
|
@@ -895,6 +896,7 @@ Planner prompt:
|
|
|
895
896
|
- {roadmap_path} (Roadmap)
|
|
896
897
|
- {requirements_path} (Requirements)
|
|
897
898
|
- {context_path} (USER DECISIONS from /gsd:discuss-phase)
|
|
899
|
+
- **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.
|
|
898
900
|
- {research_path} (Technical Research)
|
|
899
901
|
- {PATTERNS_PATH} (Pattern Map — analog files and code excerpts, if exists)
|
|
900
902
|
- {verification_path} (Verification Gaps - if --gaps)
|
package/package.json
CHANGED