@tekyzinc/gsd-t 2.34.11 → 2.35.10

package/commands/gsd-t-feature.md

@@ -22,6 +22,14 @@ Read everything:
 
 Build a mental model of: "How does this codebase work today?"
 
+**Multi-Client Architecture Check**: Before moving to Step 2, identify whether the project has or will have multiple consumer surfaces:
+- Look for directories: `web/`, `mobile/`, `app/`, `cli/`, `client/`, `frontend/`
+- Look for split route files: `routes/web.js`, `routes/mobile.js`, `routes/api/v1/`, `routes/api/v2/`
+- Check package.json scripts for `build:web`, `build:mobile`, `start:mobile`, etc.
+- Check `.gsd-t/scan/quality.md` (if exists) for the "Consumer Surfaces Detected" table
+
+Note what you find — this informs Step 3's Multi-Consumer Check and Step 4's milestone ordering.
+
 ## Step 2: Understand the Feature
 
 From $ARGUMENTS and conversation:
@@ -102,6 +110,14 @@ Produce a combined analysis:
 - {where this feature could break existing functionality}
 - {complex integration points}
 - {performance concerns}
+
+### Multi-Consumer Check
+- Consumer surfaces that exist or will exist after this feature: {list}
+- Does this feature add a new consumer surface? {yes/no}
+- If yes: backend operations this new surface needs: {list}
+- Of those, how many are already implemented for an existing surface? {list any matches}
+- SharedCore extraction candidates (operations needed by 2+ surfaces): {list or "none found"}
+- SharedCore milestone required? {yes — if 2+ candidates found | no — if none}
 ```
 
 ## Step 4: Decompose into Milestones
@@ -121,6 +137,7 @@ Apply these sequencing rules:
 3. **Existing contract updates early**: If existing contracts change, update and verify them before building new code against them
 4. **New functionality before integration**: Build the new thing, then wire it into existing flows
 5. **Migration/backfill as its own milestone**: If existing data needs transformation, isolate that work
+6. **SharedCore before new consumer surfaces**: If the feature adds a new consumer surface (web, mobile, CLI) AND SharedCore candidates were identified in Step 3's Multi-Consumer Check, add a SharedCore milestone BEFORE the new client's milestone. The SharedCore milestone extracts shared operations into a reusable backend domain — the new client's API calls SharedCore functions, it does not duplicate them.
 
 ### Write the Feature Roadmap
 

package/commands/gsd-t-partition.md

@@ -8,6 +8,8 @@ Read these files in order:
 1. `CLAUDE.md` — project conventions and context
 2. `.gsd-t/progress.md` — current state (if exists)
 3. `docs/` — all available documentation (requirements, architecture, schema, design)
+4. `.gsd-t/scan/quality.md` (if exists) — extract the "Consumer Surfaces Detected" and "Shared Service Candidates" tables. These pre-populate Step 1.6 with scan-discovered data and eliminate re-research.
+5. `.gsd-t/contracts/shared-services-contract.md` (if exists) — a SharedCore domain was previously identified. Its listed operations are pre-confirmed shared and carry forward automatically to Step 1.6.2.
 
 If `.gsd-t/` doesn't exist, create the full directory structure:
 ```
@@ -98,7 +100,11 @@ For each surface that will consume this system, capture:
 
 **Surface types**: `web`, `mobile`, `cli`, `external-api`, `admin`, `background-worker`, `other`
 
-If only one surface exists → mark "Single consumer — SharedCore not needed" and proceed to Step 2.
+**Existing System Check**: This milestone may be adding a NEW surface to a system that already has existing consumer surfaces. Before concluding surface enumeration, scan `.gsd-t/progress.md` completed milestones and look for directories or route files indicating prior client surfaces (`web/`, `mobile/`, `app/`, `cli/`, `client/`, `routes/web.js`, `routes/mobile.js`). Add any discovered existing surfaces to the table above.
+
+> ⚠️ **New-client signal**: If this milestone adds a consumer surface to a system that already has one or more other consumer surfaces, SharedCore evaluation is MANDATORY regardless of shared operation count.
+
+If only one surface exists and no prior surfaces were found → mark "Single consumer — SharedCore not needed" and proceed to Step 2.
 
 ---
 
@@ -123,7 +129,7 @@ Compare the "Operations Needed" column across all surfaces. Flag every operation
 
 ### 1.6.3 — Auto-Suggest SharedCore Domain
 
-**If 3 or more shared operations exist:**
+**If 2 or more shared operations exist, OR if this milestone adds a new consumer surface to a system that already has other surfaces (detected in the Existing System Check above):**
 
 > ⚠️ **SharedCore recommended** — {N} operations are needed by {M} consumer surfaces.
 > A `shared-core` domain will be added to own these functions.
@@ -134,7 +140,7 @@ Add `shared-core` to the domain list before running Step 2. The `shared-core` do
 - Consumed by: all surface-specific adapter domains
 - Contract: `shared-services-contract.md` (use the template from `templates/shared-services-contract.md`)
 
-**If fewer than 3 shared operations exist:**
+**If only 1 shared operation exists AND this is not a new-client-to-existing-system scenario:**
 
 > ℹ️ {N} shared operations found. Inline sharing is sufficient — no separate SharedCore domain needed. Document shared functions in the relevant domain's constraints.md.
 

package/commands/gsd-t-plan.md

@@ -18,6 +18,13 @@ Read ALL of these:
 
 ## Step 2: Create Task Lists Per Domain
 
+### SharedCore-First Pre-Check
+
+Before writing any domain task lists:
+1. Does `.gsd-t/contracts/shared-services-contract.md` exist?
+   - **YES**: A `shared-core` domain has been identified. Plan its tasks first. All client-surface domains that consume SharedCore operations are BLOCKED BY shared-core until its tasks complete. Use `BLOCKED BY shared-core Task {N}` in the relevant client domain task lists.
+   - **NO**: Proceed. The Cross-Domain Duplicate Operation Scan (below) will catch any shared operations missed during partition.
+
 For each domain, write `.gsd-t/domains/{domain-name}/tasks.md`:
 
 ```markdown
@@ -81,6 +88,19 @@ For each operation in each domain's task list:
 
 > ✅ No duplicate operations detected across domains.
 
+### SharedCore Contract Compliance Check
+
+If `.gsd-t/contracts/shared-services-contract.md` exists, run a second pass:
+
+For each client-surface domain's task list, compare task operations against the SharedCore contract's "Shared Operations" table. Flag any task that implements an operation already owned by SharedCore:
+
+> ⚠️ **SharedCore contract violation** — the following tasks reimplement operations owned by SharedCore:
+> - {domain} Task {N}: implements `{operation}` — already owned by SharedCore per shared-services-contract.md
+>
+> Fix: Change these tasks to CALL the SharedCore function rather than implementing it independently.
+
+If no violations: `✅ All client domains reference SharedCore correctly.`
+
 ---
 
 ### REQ Traceability

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "2.34.11",
+  "version": "2.35.10",
   "description": "GSD-T: Contract-Driven Development for Claude Code — 48 slash commands with real-time agent dashboard, execution intelligence, backlog management, impact analysis, test sync, milestone archival, and PRD generation",
   "author": "Tekyz, Inc.",
   "license": "MIT",