gsdd-cli 0.26.0 → 0.28.0

package/distilled/README.md

@@ -1,6 +1,6 @@
 # Workspine
 
-A repo-native delivery spine for the part of AI coding that still needs human judgment: planning, checking, execution, verification, and handoff.
+Plan, execute, and verify AI-assisted work from files in your repo — for the part of AI coding that still needs human judgment: planning, checking, execution, verification, and handoff.
 
 Workspine keeps planning, execution, verification, handoff, and progress state in the repo so work survives cold starts, runtime switches, and session loss. The retained package and CLI contracts remain `gsdd-cli` / `gsdd`.
 
@@ -25,20 +25,20 @@ Skip the full lifecycle for tiny, obvious edits. Direct prompting in your usual
 ## What This Is
 
 Workspine is a small set of workflow sources plus a CLI (`gsdd`) that:
-- scaffolds a project planning workspace (`.planning/`)
+- scaffolds a project planning workspace (`.work/`)
 - generates compact open-standard workflow entrypoints as skills (`.agents/skills/gsdd-*/SKILL.md`)
-- generates an internal repo-local helper runtime at `.planning/bin/gsdd.mjs` for deterministic workflow commands run from the repo root
+- generates an internal repo-local helper runtime at `.work/bin/gsdd.mjs` for deterministic workflow commands run from the repo root
 - optionally generates tool-specific adapters for runtimes that need extra native surfaces (root `AGENTS.md`, Claude skills + plan-command alias + native agents, OpenCode commands + native agents, Codex CLI checker agent)
 
-It gives serious AI-assisted work one durable repo workflow spine for planning, checking, execution, verification, and handoff without pretending to be a hosted orchestration layer.
+It gives serious AI-assisted work one durable, repo-native workflow for planning, checking, execution, verification, and handoff — plain files, no hosted service.
 
-Workspine is the product name. The package, CLI commands, workflow prefixes, and workspace directory remain `gsdd-cli`, `gsdd`, `gsdd-*`, and `.planning/` — these are retained technical contracts, not rename residue.
+Workspine is the product name. The package, CLI commands, workflow prefixes, and workspace directory remain `gsdd-cli`, `gsdd`, `gsdd-*`, and `.work/`; legacy `.planning/` workspaces are still read.
 
-Workspine began as a fork of Get Shit Done, whose long-horizon delivery spine proved the problem was real. Since the fork, upstream GSD has continued evolving into a broad multi-runtime framework. Workspine took a different path: a smaller repo-native delivery spine with fewer public workflow surfaces, generated runtime surfaces from a portable core, evidence-gated closure, and provenance-aware continuity.
+Workspine began as a fork of Get Shit Done, whose long-horizon workflow proved the problem was real. Since the fork, upstream GSD has continued evolving into a broad multi-runtime framework. Workspine took a different path: a smaller repo-native tool with fewer public workflows, generated runtime surfaces from a portable core, proof required before closing work, and decisions that keep their why.
 
 Launch proof posture:
-- Directly validated in repo truth: Claude Code, Codex CLI, OpenCode
-- Qualified support only: Cursor, Copilot, Gemini CLI can use the shared `.agents/skills/` surface plus optional governance when their skill or slash discovery sees it; proof and ergonomics differ from the directly validated runtimes
+- Recorded launch proof in repo truth currently covers Claude Code, Codex CLI, and OpenCode paths
+- Qualified support only: Cursor, Copilot, Gemini CLI can use the shared `.agents/skills/` surface plus optional governance when their skill or slash discovery sees it; proof and ergonomics differ from the recorded paths above
 - Codex CLI validation does not automatically cover Codex VS Code or the Codex app; use native discovery there when available, otherwise open or paste `.agents/skills/gsdd-*/SKILL.md`
 - Repo-local generated runtime surfaces are renderer-checked through `npx -y gsdd-cli health`, with deterministic repair through `npx -y gsdd-cli update` (bare `gsdd ...` is equivalent only when globally installed)
 - Public proof entrypoints: `docs/BROWNFIELD-PROOF.md`, `docs/proof/consumer-node-cli/README.md`, `docs/RUNTIME-SUPPORT.md`, `docs/VERIFICATION-DISCIPLINE.md`
@@ -59,7 +59,7 @@ npx -y gsdd-cli install --global
 npx -y gsdd-cli install --global --tools claude,opencode,codex,copilot
 ```
 
-Global install writes selected Workspine skills and native agent surfaces into user-level agent homes. It does not create `.planning/` in the current repo.
+Global install writes selected Workspine skills and native agent surfaces into user-level agent homes. It does not create `.work/` in the current repo.
 
 Optional adapters:
 ```bash
@@ -72,18 +72,18 @@ npx -y gsdd-cli init --tools all
 ```
 
 Notes:
-- `npx -y gsdd-cli init` always generates open-standard skills at `.agents/skills/gsdd-*` plus the repo-local helper runtime at `.planning/bin/gsdd.mjs`. Workflow helper commands assume the repo root as the current working directory.
+- `npx -y gsdd-cli init` always generates open-standard skills at `.agents/skills/gsdd-*` plus the repo-local helper runtime at `.work/bin/gsdd.mjs`. Workflow helper commands assume the repo root as the current working directory.
 - `--tools ...` remains the manual/headless path; legacy runtime aliases such as `cursor`, `copilot`, and `gemini` are still supported for backward compatibility.
 - `--tools claude` also generates native agents at `.claude/agents/gsdd-*.md` and a compatibility plan command alias at `.claude/commands/gsdd-plan.md`.
 - `--tools opencode` also generates native agents at `.opencode/agents/gsdd-*.md`.
-- `--tools codex` generates `.codex/agents/gsdd-plan-checker.toml`; the portable `.agents/skills/gsdd-plan/` surface remains the Codex entry path and internal helper commands route through `.planning/bin/gsdd.mjs`.
+- `--tools codex` generates `.codex/agents/gsdd-plan-checker.toml`; the portable `.agents/skills/gsdd-plan/` surface remains the Codex entry path and internal helper commands route through `.work/bin/gsdd.mjs`.
 - Root `AGENTS.md` is only written when explicitly requested (`--tools agents`, `--tools all`, legacy runtime aliases, or the wizard governance opt-in). Governance and native adapter surfaces are optional ergonomics; the compact `.agents/skills/` files remain the baseline agent entrypoints.
 
 ## The Workflow
 
 ```
-npx -y gsdd-cli init       -> bootstrap (create .planning/, copy templates, generate skills/adapters)
-/gsdd-new-project          -> .planning/SPEC.md + .planning/ROADMAP.md  (questioning + codebase audit + research)
+npx -y gsdd-cli init       -> bootstrap (create .work/, copy templates, generate skills/adapters)
+/gsdd-new-project          -> .work/SPEC.md + .work/ROADMAP.md  (questioning + codebase audit + research)
 /gsdd-plan N               -> phases/N/PLAN.md      (task breakdown + research)
 /gsdd-execute N            -> code changes           (plan execution with quality gates)
 /gsdd-verify N             -> VERIFICATION.md        (goal-backward validation)
@@ -91,23 +91,15 @@ npx -y gsdd-cli init       -> bootstrap (create .planning/, copy templates, gene
 /gsdd-audit-milestone      -> MILESTONE-AUDIT.md     (cross-phase integration + requirements coverage)
 /gsdd-complete-milestone   -> milestones/vX.Y-*      (archive, evolve spec, collapse roadmap)
 /gsdd-new-milestone        -> updated SPEC.md + ROADMAP.md  (next milestone goals + phases)
-/gsdd-plan-milestone-gaps  -> gap closure phases in ROADMAP.md  (from audit results)
-/gsdd-quick                -> .planning/quick/NNN/   (sub-hour task outside phases)
-/gsdd-pause                -> .planning/.continue-here.md  (session checkpoint)
+/gsdd-plan                 -> amend/extend gap closure phases in ROADMAP.md  (from audit results)
+/gsdd-quick                -> .work/quick/NNN/   (sub-hour task outside phases)
+/gsdd-pause                -> .work/.continue-here.md  (session checkpoint)
 /gsdd-resume               -> restore context, route to next action
 /gsdd-progress             -> show status, route to next action
 ```
 
 The main operator spine is four workflow moves after bootstrap: `new-project -> plan -> execute -> verify`. The other public workflow surfaces are support lanes for milestone closeout, quick work, progress, pause/resume, and brownfield orientation.
 
-Helper command for long-running sessions:
-
-```
-npx -y gsdd-cli control-map [--json] [--with-ignored] -> computed repo/worktree/planning state plus local annotations
-npx -y gsdd-cli control-map annotate set|clear -> optional stale-aware local intent maintenance
-npx -y gsdd-cli closeout-report [--json] [--phase <N>] -> read-only replay of closeout blockers, warnings, fixes, and next safe action
-```
-
 ## Brownfield Entry Contract
 
 Use the same three-way routing everywhere:
@@ -127,7 +119,7 @@ Use the same three-way routing everywhere:
 | `audit-milestone.md` | Cross-phase integration audit, auth protection checks, requirement reconciliation, and orphan detection into `MILESTONE-AUDIT.md` |
 | `complete-milestone.md` | Milestone archive, spec evolution, and roadmap collapse |
 | `new-milestone.md` | Brownfield milestone continuation: goals, requirements, and roadmap phases |
-| `plan-milestone-gaps.md` | Gap-closure phases from `MILESTONE-AUDIT.md` results |
+| `plan.md` amend/extend mode | Gap-closure phases from `MILESTONE-AUDIT.md`, verification gaps, tech debt, brownfield amendments, or incident docs |
 | `quick.md` | Quick-work lane for sub-hour tasks outside the phase cycle |
 | `pause.md` | Session checkpoint writer with conversational handoff |
 | `resume.md` | Session context restorer with priority-ordered routing |
@@ -137,8 +129,8 @@ Use the same three-way routing everywhere:
 
 Architecture notes:
 - `bin/gsdd.mjs` remains the thin generator entrypoint, while vendor-specific rendering lives in adapter modules.
-- Codex CLI uses the always-generated `.agents/skills/gsdd-*` surface as its entry path, relies on `.planning/bin/gsdd.mjs` for deterministic helper calls, and can add a native `.codex/agents/gsdd-plan-checker.toml` checker agent.
-- `control-map` is a helper command, not a lifecycle workflow: it computes repo/worktree/planning truth first and treats `.planning/.local/` annotations as local intent only. `control-map annotate` can maintain those annotations, but cannot create ownership, cleanup, or lifecycle authority.
+- Codex CLI uses the always-generated `.agents/skills/gsdd-*` surface as its entry path, relies on `.work/bin/gsdd.mjs` for deterministic helper calls, and can add a native `.codex/agents/gsdd-plan-checker.toml` checker agent.
+- Repo/worktree status helpers compute from git and local workflow state first; local annotations are intent hints only and cannot create ownership, cleanup, or lifecycle authority.
 - Codex VS Code/app are separate surfaces from Codex CLI; do not claim the CLI proof for them unless they expose compatible skill discovery. Fallback is opening or pasting the generated `SKILL.md`.
 - `npx -y gsdd-cli health` now compares any installed generated runtime surfaces against current render output and routes repairs back through `npx -y gsdd-cli update`.
 - Portable lifecycle contracts now align to the roadmap template status grammar: `[ ]`, `[-]`, `[x]`.
@@ -162,7 +154,7 @@ Note: `parallelization: false` keeps the same mapper/researcher set but runs the
 ## What Gets Created (Project Output)
 
 ```
-.planning/
+.work/
   SPEC.md
   ROADMAP.md
   config.json
@@ -173,7 +165,6 @@ Note: `parallelization: false` keeps the same mapper/researcher set but runs the
   gsdd-new-project/SKILL.md
   gsdd-new-milestone/SKILL.md
   gsdd-plan/SKILL.md
-  gsdd-plan-milestone-gaps/SKILL.md
   gsdd-execute/SKILL.md
   gsdd-verify/SKILL.md
   gsdd-verify-work/SKILL.md
@@ -196,7 +187,7 @@ Note: `parallelization: false` keeps the same mapper/researcher set but runs the
   gsdd-plan.md              # OpenCode-native specialized planner -> checker command surface
 .codex/agents/
   gsdd-plan-checker.toml    # Codex-native checker agent (read-only, high reasoning effort)
-.planning/
+.work/
   quick/              # quick task directories and LOG.md
   .continue-here.md   # session checkpoint (created by pause)
 ```
@@ -217,7 +208,6 @@ distilled/
     new-milestone.md
     pause.md
     plan.md
-    plan-milestone-gaps.md
     progress.md
     quick.md
     resume.md
@@ -227,8 +217,8 @@ distilled/
     spec.md
     roadmap.md
     agents.md              # full AGENTS.md template (for tool adapters)
-    agents.block.md        # bounded block payload for root AGENTS.md insertion
-    delegates/             # delegate instruction files (copied to .planning/templates/delegates/)
+    agents.block.md        # managed payload for root AGENTS.md insertion
+    delegates/             # delegate instruction files (copied to .work/templates/delegates/)
       mapper-tech.md
       mapper-arch.md
       mapper-quality.md

package/distilled/SKILL.md

@@ -31,13 +31,12 @@ Read only the file for the phase you are in:
 - audit-milestone: `workflows/audit-milestone.md`
 - complete-milestone: `workflows/complete-milestone.md`
 - new-milestone: `workflows/new-milestone.md`
-- plan-milestone-gaps: `workflows/plan-milestone-gaps.md`
 - quick: `workflows/quick.md`
 </workflow>
 
 <governance>
 Mandatory:
-- Read before you write. If `.planning/` exists, read `.planning/SPEC.md`, `.planning/ROADMAP.md`, `.planning/config.json`.
+- Read before you write. If `.work/` exists, read `.work/SPEC.md`, `.work/ROADMAP.md`, `.work/config.json`; use matching `.planning/` paths only in legacy workspaces.
 - Stay in scope. Implement only what the current phase plan describes.
 - Never hallucinate. Confirm paths and APIs from repo or docs before use.
 - Research-first when unfamiliar. Log evidence, then plan.
@@ -45,10 +44,10 @@ Mandatory:
 </governance>
 
 <project_structure>
-Workspine uses `.planning/` as the durable workspace:
+Workspine uses `.work/` as the durable workspace. Legacy `.planning/` workspaces are still read and supported.
 
 ```
-.planning/
+.work/
   SPEC.md
   ROADMAP.md
   config.json
@@ -69,22 +68,22 @@ npx -y gsdd-cli init --tools agents
 ```
 
 Behavior:
-- Always: generates open-standard skills at `.agents/skills/gsdd-*/SKILL.md` by embedding `distilled/workflows/*.md`, plus repo-local deterministic helpers at `.planning/bin/gsdd.mjs`.
+- Always: generates open-standard skills at `.agents/skills/gsdd-*/SKILL.md` by embedding `distilled/workflows/*.md`, plus repo-local deterministic helpers at `.work/bin/gsdd.mjs` (or `.planning/bin/gsdd.mjs` in legacy workspaces).
 - Optional: generates tool adapters (root `AGENTS.md`, Claude `.claude/skills` + `.claude/commands` alias + `.claude/agents`, OpenCode `.opencode/commands` + `.opencode/agents`, Codex CLI `.codex/agents/gsdd-plan-checker.toml`).
 - Codex CLI: uses the portable skill entry surface and the generated `.codex/agents/` checker/approach-explorer agents; it does not use `.codex/AGENTS.md` as the primary integration path.
 - Root `AGENTS.md` is only written when explicitly requested (so we do not pollute existing user governance).
 </adapters>
 
 <templates>
-Use templates from `.planning/templates/` (copied from `distilled/templates/`) when producing planning artifacts.
+Use templates from `.work/templates/` (copied from `distilled/templates/`) when producing planning artifacts; use `.planning/templates/` only in legacy workspaces.
 
 Core:
-- `.planning/templates/spec.md` -> `.planning/SPEC.md`
-- `.planning/templates/roadmap.md` -> `.planning/ROADMAP.md`
+- `.work/templates/spec.md` -> `.work/SPEC.md`
+- `.work/templates/roadmap.md` -> `.work/ROADMAP.md`
 
 Research:
-- `.planning/templates/research/*.md` -> `.planning/research/*.md`
+- `.work/templates/research/*.md` -> `.work/research/*.md`
 
 Brownfield codebase mapping:
-- `.planning/templates/codebase/*.md` -> `.planning/codebase/*.md`
+- `.work/templates/codebase/*.md` -> `.work/codebase/*.md`
 </templates>

package/distilled/templates/agents.block.md

@@ -5,17 +5,17 @@ Managed by `gsdd`; edit the framework template, not this block.
 Lifecycle: `new-project -> plan -> execute -> verify -> audit-milestone`.
 
 Core skills: `gsdd-new-project`, `gsdd-plan`, `gsdd-execute`, `gsdd-verify`, `gsdd-progress`.
-Planning state: `.planning/`. Portable workflows: `.agents/skills/gsdd-*/SKILL.md`.
+Planning state: `.work/` (legacy `.planning/` workspaces are still read). Portable workflows: `.agents/skills/gsdd-*/SKILL.md`.
 Install/repair: `npx -y gsdd-cli init` creates repo-local skills and planning state; `npx -y gsdd-cli health` verifies repo-local generated surfaces; `npx -y gsdd-cli update` repairs repo-local drift. Global personal skills use `npx -y gsdd-cli install --global` and are repaired by rerunning that install for the selected targets.
 
 Invoke: `/gsdd-plan` (Claude, OpenCode; Cursor/Copilot/Gemini when skill discovery is available) · `$gsdd-plan` (Codex CLI, plan-only until `$gsdd-execute`) · open SKILL.md directly elsewhere.
 
 Rules:
-1. Read before writing roadmap work: `.planning/SPEC.md`, `.planning/ROADMAP.md`, `.planning/config.json`, and the relevant phase plan when one exists.
+1. Read before writing roadmap work: `.work/SPEC.md`, `.work/ROADMAP.md`, `.work/config.json`, and the relevant phase plan when one exists; use matching `.planning/` paths only in legacy workspaces.
 2. Stay in scope. Implement only what the approved plan or direct user request says. Record unrelated ideas as TODOs.
 3. Verify before claiming done: artifact exists, content is substantive, and it is wired into the system.
 4. Research unfamiliar domains from real docs and code; never hallucinate paths or APIs.
-5. Do not pollute core workflows with vendor-specific syntax; workflow entry lives in `.agents/skills/`, helpers in `.planning/bin/`, and native adapters in their tool-specific directories.
-6. Git guidance in `.planning/config.json` -> `gitProtocol` is advisory; follow the repo's own conventions first.
+5. Do not pollute core workflows with vendor-specific syntax; workflow entry lives in `.agents/skills/`, helpers in `.work/bin/`, and native adapters in their tool-specific directories.
+6. Git guidance in `.work/config.json` -> `gitProtocol` is advisory; follow the repo's own conventions first.
 
-If `.planning/` is missing, run `npx -y gsdd-cli init` then `gsdd-new-project`; bare `gsdd init` is equivalent only when globally installed.
+If `.work/` is missing, run `npx -y gsdd-cli init` then `gsdd-new-project`; bare `gsdd init` is equivalent only when globally installed.

package/distilled/templates/approach.md

@@ -1,12 +1,12 @@
 # Phase Approach Template
 
-Template for `.planning/phases/XX-name/{phase_num}-APPROACH.md` — captures implementation decisions and validated assumptions for a phase.
+Template for `.work/phases/XX-name/{phase_num}-APPROACH.md` — captures implementation decisions and validated assumptions for a phase.
 
 **Purpose:** Document decisions that downstream agents need. Planner uses this to know WHAT choices are locked vs flexible. Plan-checker verifies plans honor these decisions.
 
 **Key principle:** The top-level structure (`<domain>`, `<decisions>`, `<assumptions>`, `<deferred>`) is fixed. Section names WITHIN `<decisions>` emerge from what was actually discussed for THIS phase — a CLI phase has CLI-relevant sections, a UI phase has UI-relevant sections.
 
-**Alignment proof:** When `.planning/config.json` has `workflow.discuss: true`, every APPROACH artifact must include an `## Alignment Proof` section before `<domain>`. It must record the canonical fields `alignment_status`, `alignment_method`, `user_confirmed_at`, `explicit_skip_approved`, `skip_scope`, `skip_rationale`, and `confirmed_decisions`. `Agent's Discretion` and agent-only "No questions needed" are not valid proof.
+**Alignment proof:** When `.work/config.json` has `workflow.discuss: true`, every APPROACH artifact must include an `## Alignment Proof` section before `<domain>`. It must record the canonical fields `alignment_status`, `alignment_method`, `user_confirmed_at`, `explicit_skip_approved`, `skip_scope`, `skip_rationale`, and `confirmed_decisions`. `Agent's Discretion` and agent-only "No questions needed" are not valid proof.
 
 **Downstream consumers:**
 - `planner` — Reads decisions to constrain implementation choices. Locked decisions must be implemented. Agent's Discretion items allow planner flexibility.
@@ -266,7 +266,7 @@ Users can register and log in with email/password. Session management via JWT. O
 The output should answer: "What choices are locked for the planner? Where does the planner have discretion?"
 
 **After creation:**
-- File lives in phase directory: `.planning/phases/XX-name/{phase_num}-APPROACH.md`
+- File lives in phase directory: `.work/phases/XX-name/{phase_num}-APPROACH.md`
 - Planner reads decisions to constrain implementation tasks
 - Plan-checker verifies approach_alignment: plans must implement chosen approaches
 - Downstream agents should NOT need to ask the user again about captured decisions

package/distilled/templates/auth-matrix.md

@@ -1,7 +1,7 @@
 # Authorization Matrix Template
 
 > OWASP-style authorization matrix for systematic auth verification.
-> Create `.planning/AUTH_MATRIX.md` using this template when your project has multiple user roles or protected resources.
+> Create `.work/AUTH_MATRIX.md` using this template when your project has multiple user roles or protected resources.
 
 ## When to Create This Matrix
 
@@ -73,6 +73,6 @@ The narrative auth check (Step 4) always runs regardless of whether this matrix
 
 ## File Location
 
-Save your project's authorization matrix as `.planning/AUTH_MATRIX.md`.
+Save your project's authorization matrix as `.work/AUTH_MATRIX.md`.
 
 The integration checker will automatically detect and consume it when present. No configuration needed.

package/distilled/templates/brownfield-change/CHANGE.md

@@ -9,7 +9,7 @@ type: medium_scope_brownfield
 > This folder is the bounded medium-scope lane.
 > It represents one active medium-scope change only.
 > Do not add phase numbering, roadmap checkboxes, or milestone state here.
-> Instantiate the live operational artifact at `.planning/brownfield-change/CHANGE.md`.
+> Instantiate the live operational artifact at `.work/brownfield-change/CHANGE.md`.
 > `progress` and `resume` read this file first for status, scope, integration surface, and the authoritative next action.
 > If this lane no longer fits one active stream, widen explicitly through `/gsdd-new-project` (first milestone) or `/gsdd-new-milestone` (subsequent milestone) using this folder as the preserved input surface. Do not invent a separate promotion artifact.
 

package/distilled/templates/delegates/approach-explorer.md

@@ -1,4 +1,4 @@
-**Role contract:** Read `.planning/templates/roles/approach-explorer.md` before starting. Follow its algorithm, scope, anti-patterns, and quality standards.
+**Role contract:** Read `.work/templates/roles/approach-explorer.md` before starting. Follow its algorithm, scope, anti-patterns, and quality standards.
 
 You are the approach explorer delegate for the plan workflow.
 
@@ -7,12 +7,12 @@ You are the approach explorer delegate for the plan workflow.
 When `workflow.discuss: true`, APPROACH.md must prove user alignment before planning: use `alignment_status: user_confirmed` for real user-confirmed decisions or `alignment_status: approved_skip` only when the user explicitly approves skipping discussion. Record the canonical fields `alignment_method`, `user_confirmed_at`, `explicit_skip_approved`, `skip_scope`, `skip_rationale`, and `confirmed_decisions`. `Agent's Discretion` and agent-only "No questions needed" are not valid alignment proof.
 
 Read only the explicit inputs provided by the orchestrator:
-- target phase goal and requirement IDs from `.planning/ROADMAP.md`
-- project config from `.planning/config.json`, especially `workflow.discuss`
-- locked decisions and deferred items from `.planning/SPEC.md`
+- target phase goal and requirement IDs from `.work/ROADMAP.md`
+- project config from `.work/config.json`, especially `workflow.discuss`
+- locked decisions and deferred items from `.work/SPEC.md`
 - phase research file (if exists)
 - relevant codebase files (existing patterns and conventions)
-- approach template at `.planning/templates/approach.md`
+- approach template at `.work/templates/approach.md`
 
 ## Gray Area Classification
 

package/distilled/templates/delegates/mapper-arch.md

@@ -1,8 +1,8 @@
-**Role contract:** Read `.planning/templates/roles/mapper.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
+**Role contract:** Read `.work/templates/roles/mapper.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
 
 Map the architecture and structure of this codebase. Read key source files to understand component boundaries, data flow, and patterns.
 
-Write ARCHITECTURE.md to `.planning/codebase/` using the template at `.planning/templates/codebase/architecture.md`.
+Write ARCHITECTURE.md to `.work/codebase/` using the template at `.work/templates/codebase/architecture.md`.
 
 Include:
 - Major components and their responsibilities (what belongs in each, what doesn't)
@@ -21,6 +21,6 @@ Include:
 - [ ] Golden files table populated with at least one file per major layer
 </quality_gate>
 
-Write to: `.planning/codebase/ARCHITECTURE.md`
+Write to: `.work/codebase/ARCHITECTURE.md`
 Return: Routing summary to the Orchestrator (100-200 tokens) when done.
 Guardrails: Max Agent Hops = 3. No static directory dumps.

package/distilled/templates/delegates/mapper-concerns.md

@@ -1,10 +1,10 @@
-**Role contract:** Read `.planning/templates/roles/mapper.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
+**Role contract:** Read `.work/templates/roles/mapper.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
 
 Map the technical debt, security concerns, and risks in this codebase.
 
-**Security check first (hard stop):** Follow the Hard stop directive in `.planning/templates/roles/mapper.md` — grep for secrets before writing anything. If found: STOP and report to Orchestrator immediately.
+**Security check first (hard stop):** Follow the Hard stop directive in `.work/templates/roles/mapper.md` — grep for secrets before writing anything. If found: STOP and report to Orchestrator immediately.
 
-If no secrets found, write CONCERNS.md to `.planning/codebase/` using the template at `.planning/templates/codebase/concerns.md`.
+If no secrets found, write CONCERNS.md to `.work/codebase/` using the template at `.work/templates/codebase/concerns.md`.
 
 Include:
 - Known bugs or fragile areas (with file references where possible)
@@ -22,6 +22,6 @@ Include:
 - [ ] Downstream impact table ranks at least top 3 concerns with Blocks column populated
 </quality_gate>
 
-Write to: `.planning/codebase/CONCERNS.md`
+Write to: `.work/codebase/CONCERNS.md`
 Return: Routing summary to the Orchestrator (100-200 tokens) when done. If secrets found, STOP and report immediately.
 Guardrails: Max Agent Hops = 3. Hard stop on secrets.

package/distilled/templates/delegates/mapper-quality.md

@@ -1,8 +1,8 @@
-**Role contract:** Read `.planning/templates/roles/mapper.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
+**Role contract:** Read `.work/templates/roles/mapper.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
 
 Map the conventions and quality patterns of this codebase. Read existing tests, lint config, and code samples.
 
-Write CONVENTIONS.md to `.planning/codebase/` using the template at `.planning/templates/codebase/conventions.md`.
+Write CONVENTIONS.md to `.work/codebase/` using the template at `.work/templates/codebase/conventions.md`.
 
 Include:
 - Naming patterns (files, functions, variables, exports)
@@ -23,6 +23,6 @@ Include:
 - [ ] Golden files section lists at least 2 files with rationale
 </quality_gate>
 
-Write to: `.planning/codebase/CONVENTIONS.md`
+Write to: `.work/codebase/CONVENTIONS.md`
 Return: Routing summary to the Orchestrator (100-200 tokens) when done.
 Guardrails: Max Agent Hops = 3. Rules not inventories.

package/distilled/templates/delegates/mapper-tech.md

@@ -1,8 +1,8 @@
-**Role contract:** Read `.planning/templates/roles/mapper.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
+**Role contract:** Read `.work/templates/roles/mapper.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
 
 Map the technology stack of this codebase. Read package manifests, lockfiles, and entry points.
 
-Write STACK.md to `.planning/codebase/` using the template at `.planning/templates/codebase/stack.md`.
+Write STACK.md to `.work/codebase/` using the template at `.work/templates/codebase/stack.md`.
 
 Include:
 - Languages and runtimes (with versions)
@@ -20,6 +20,6 @@ Include:
 - [ ] Must-know packages section identifies at least 3 packages with risk index (low/medium/high)
 </quality_gate>
 
-Write to: `.planning/codebase/STACK.md`
+Write to: `.work/codebase/STACK.md`
 Return: Routing summary to the Orchestrator (100-200 tokens) when done.
 Guardrails: Max Agent Hops = 3. No static dependency dumps.

package/distilled/templates/delegates/plan-checker.md

@@ -1,14 +1,14 @@
-**Role contract:** Read `.planning/templates/roles/planner.md` before starting. Reuse its planning vocabulary and quality standards, but this wrapper overrides your objective: you are reviewing plans, not authoring them.
+**Role contract:** Read `.work/templates/roles/planner.md` before starting. Reuse its planning vocabulary and quality standards, but this wrapper overrides your objective: you are reviewing plans, not authoring them.
 
 You are the fresh-context plan checker for `/gsdd-plan`. This is a read-only review delegate: return the JSON finding summary only, and do not edit plan artifacts yourself.
 
 Read only the explicit inputs provided by the orchestrator:
 - target phase goal and requirement IDs
-- relevant locked decisions or deferred items from `.planning/SPEC.md`
-- project config from `.planning/config.json`, especially `workflow.discuss` and `workflow.planCheck`
-- approach decisions from `.planning/phases/*-APPROACH.md` (if provided)
+- relevant locked decisions or deferred items from `.work/SPEC.md`
+- project config from `.work/config.json`, especially `workflow.discuss` and `workflow.planCheck`
+- approach decisions from `.work/phases/*-APPROACH.md` (if provided)
 - any relevant phase research file
-- the produced `.planning/phases/*-PLAN.md` file(s)
+- the produced `.work/phases/*-PLAN.md` file(s)
 
 Do NOT inherit the planner's hidden reasoning. Treat the current plans as untrusted drafts that must prove they will achieve the phase goal before execution.
 

package/distilled/templates/delegates/researcher-architecture.md

@@ -1,4 +1,4 @@
-**Role contract:** Read `.planning/templates/roles/researcher.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
+**Role contract:** Read `.work/templates/roles/researcher.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
 
 You are researching ONE dimension: how systems in this domain are typically structured.
 
@@ -24,7 +24,7 @@ Your output informs phase structure in ROADMAP.md. Include:
 - [ ] Hard-to-reverse decisions flagged explicitly
 </quality_gate>
 
-Write to: `.planning/research/ARCHITECTURE.md`
-Use template: `.planning/templates/research/architecture.md` (if it exists)
+Write to: `.work/research/ARCHITECTURE.md`
+Use template: `.work/templates/research/architecture.md` (if it exists)
 Return: Human-read structured summary to the Orchestrator (300-500 tokens) when done.
 Guardrails: Max Agent Hops = 3.

package/distilled/templates/delegates/researcher-features.md

@@ -1,4 +1,4 @@
-**Role contract:** Read `.planning/templates/roles/researcher.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
+**Role contract:** Read `.work/templates/roles/researcher.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
 
 You are researching ONE dimension: what features exist in this domain.
 
@@ -24,7 +24,7 @@ Your output feeds SPEC requirements. Categorize explicitly:
 - [ ] v1 vs v2 recommendation for differentiators
 </quality_gate>
 
-Write to: `.planning/research/FEATURES.md`
-Use template: `.planning/templates/research/features.md` (if it exists)
+Write to: `.work/research/FEATURES.md`
+Use template: `.work/templates/research/features.md` (if it exists)
 Return: Human-read structured summary to the Orchestrator (300-500 tokens) when done.
 Guardrails: Max Agent Hops = 3.

package/distilled/templates/delegates/researcher-pitfalls.md

@@ -1,4 +1,4 @@
-**Role contract:** Read `.planning/templates/roles/researcher.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
+**Role contract:** Read `.work/templates/roles/researcher.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
 
 You are researching ONE dimension: what goes wrong in projects in this domain.
 
@@ -24,7 +24,7 @@ Your output prevents mistakes in roadmap and planning. For each pitfall:
 - [ ] Sources cited for non-obvious claims
 </quality_gate>
 
-Write to: `.planning/research/PITFALLS.md`
-Use template: `.planning/templates/research/pitfalls.md` (if it exists)
+Write to: `.work/research/PITFALLS.md`
+Use template: `.work/templates/research/pitfalls.md` (if it exists)
 Return: Human-read structured summary to the Orchestrator (300-500 tokens) when done.
 Guardrails: Max Agent Hops = 3.

package/distilled/templates/delegates/researcher-stack.md

@@ -1,4 +1,4 @@
-**Role contract:** Read `.planning/templates/roles/researcher.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
+**Role contract:** Read `.work/templates/roles/researcher.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
 
 You are researching ONE dimension: the technology stack for the project domain.
 
@@ -24,7 +24,7 @@ Your output feeds the roadmapper. Be prescriptive:
 - [ ] Confidence level assigned to each recommendation
 </quality_gate>
 
-Write to: `.planning/research/STACK.md`
-Use template: `.planning/templates/research/stack.md` (if it exists)
+Write to: `.work/research/STACK.md`
+Use template: `.work/templates/research/stack.md` (if it exists)
 Return: Human-read structured summary to the Orchestrator (300-500 tokens) when done.
 Guardrails: Max Agent Hops = 3.

package/distilled/templates/delegates/researcher-synthesizer.md

@@ -1,12 +1,12 @@
-**Role contract:** Read `.planning/templates/roles/synthesizer.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
+**Role contract:** Read `.work/templates/roles/synthesizer.md` before starting. Follow its algorithm, quality guarantees, and anti-patterns.
 
 Synthesize the 4 research files into a single actionable SUMMARY.md.
 
 Read these files (all should exist):
-- `.planning/research/STACK.md`
-- `.planning/research/FEATURES.md`
-- `.planning/research/ARCHITECTURE.md`
-- `.planning/research/PITFALLS.md`
+- `.work/research/STACK.md`
+- `.work/research/FEATURES.md`
+- `.work/research/ARCHITECTURE.md`
+- `.work/research/PITFALLS.md`
 
 Cross-reference them. Surface conflicts and dependencies between findings. Do NOT do new research — synthesize what exists.
 
@@ -17,7 +17,7 @@ SUMMARY.md MUST include:
 4. **Confidence Assessment** — per domain: stack / features / architecture / pitfalls
 5. **Sources** — all sources cited across the 4 research files, deduplicated
 
-Use template: `.planning/templates/research/summary.md` (if it exists)
+Use template: `.work/templates/research/summary.md` (if it exists)
 
 <quality_gate>
 - [ ] "Implications for Roadmap" section populated with phase suggestions
@@ -26,6 +26,6 @@ Use template: `.planning/templates/research/summary.md` (if it exists)
 - [ ] No new claims introduced (only synthesis)
 </quality_gate>
 
-Write to: `.planning/research/SUMMARY.md`
+Write to: `.work/research/SUMMARY.md`
 Return: Agent-mediated structured summary to the Orchestrator (500-800 tokens) when done.
 Guardrails: Max Agent Hops = 2. Do not do new research — synthesize only.

package/distilled/templates/research/architecture.md

@@ -2,7 +2,7 @@
 
 Use when researching system structure and patterns for a project or phase.
 
-Write to: `.planning/research/ARCHITECTURE.md`
+Write to: `.work/research/ARCHITECTURE.md`
 
 ---
 

package/distilled/templates/research/pitfalls.md

@@ -2,7 +2,7 @@
 
 Use when researching common mistakes and gotchas for a domain or technology.
 
-Write to: `.planning/research/PITFALLS.md`
+Write to: `.work/research/PITFALLS.md`
 
 ---
 

package/distilled/templates/research/stack.md

@@ -2,7 +2,7 @@
 
 Use when researching the technology stack for a project or phase.
 
-Write to: `.planning/research/STACK.md`
+Write to: `.work/research/STACK.md`
 
 ---
 

package/distilled/templates/roadmap.md

@@ -1,6 +1,6 @@
 # ROADMAP.md Template
 
-Use this template when creating `.planning/ROADMAP.md` (phase breakdown + progress tracker).
+Use this template when creating `.work/ROADMAP.md` (phase breakdown + progress tracker).
 
 ```markdown
 # Roadmap: [Project Name]
@@ -21,7 +21,7 @@ Use this template when creating `.planning/ROADMAP.md` (phase breakdown + progre
 
 **Goal**: [What this phase delivers]
 **Status**: [ ]
-**Requirements**: [REQ-IDs from `.planning/SPEC.md`]
+**Requirements**: [REQ-IDs from `.work/SPEC.md`]
 **Success Criteria** (must be TRUE when done):
 1. [Observable behavior]
 2. [Observable behavior]
@@ -53,7 +53,7 @@ Use this template when creating `.planning/ROADMAP.md` (phase breakdown + progre
 ## Guidelines
 
 - Prefer 3-8 phases for most projects.
-- Every v1 requirement in `.planning/SPEC.md` must map to exactly one phase (no orphans).
+- Every v1 requirement in `.work/SPEC.md` must map to exactly one phase (no orphans).
 - Success criteria are 2-5 observable behaviors per phase.
 - No time estimates: focus on verifiable outcomes.
 - These status markers are the portable source of truth. Workflow files and summaries should use `[ ]`, `[-]`, and `[x]` consistently.
@@ -64,7 +64,7 @@ Use this template when creating `.planning/ROADMAP.md` (phase breakdown + progre
 
 After creating the roadmap, verify:
 ```
-For each v1 requirement in .planning/SPEC.md:
+For each v1 requirement in .work/SPEC.md:
   [ ] Requirement appears in exactly one phase's "Requirements" list
   [ ] The phase's success criteria would prove the requirement is met
 ```

package/distilled/templates/spec.md

@@ -1,6 +1,6 @@
 # SPEC.md Template
 
-Use this template when creating `.planning/SPEC.md` - the project's single source of truth.
+Use this template when creating `.work/SPEC.md` - the project's single source of truth.
 
 > **Agentic PRD Constraint:** Do not write narrative prose or fluff. Use strict checklists, dense tables, and typed schemas. There is no artificial line limit, but every single line must be highly deterministic and actionable for a downstream Subagent.
 
@@ -105,5 +105,5 @@ If auditing an existing codebase during `init`:
 
 When a major milestone completes:
 1. The SPEC.md "Current State" section reflects the new state
-2. Completed phases have summaries in `.planning/phases/{N}-SUMMARY.md`
+2. Completed phases have summaries in `.work/phases/{N}-SUMMARY.md`
 3. SPEC.md itself stays lean - don't accumulate history here