open-gsd/get-shit-done-redux

@jnuyens one other request, please look in docs/dev/adr.

These are 'architecture design records' and they will save your standards (names, variables, logic, etc) if you name them in the GitHub slug format when you PR they will take the PR # assigned. This helps with future updates fixes, feel free to look at the ones I've worked on they are mostly agent read/written and help keep future things in line. Eventually I will enforce them.

If you could do me a favor and target the 'next' branch for the PR, I'm working on createing/updating a 'real' plan where stuff no longer commits to main. I'm working on wrapping up one thing before I do it, contributors.md should have the 'future state' in them

Follow-up from real-project use of `/gsd-new-ddd` (shipped downstream in plugin v2.44.0). Three findings, two of which extend this enhancement and one which is a sibling bug filed separately as #222 (synthesizer write-restriction hallucination, affects standard `/gsd-new-project` too).

Two DDD-specific changes shipped in plugin v2.44.3 ([commit 63283af](https://github.com/jnuyens/gsd-plugin/commit/63283af)) that should fold into the eventual upstream landing of this enhancement:

## Change 1: SPEC file path moved from `.planning/DOCS.md` to `docs/SPEC.md`

The original v2.44.0 sketch put the spec at `.planning/DOCS.md`. Real use surfaced two problems:

1. `.planning/` is the GSD-internal directory, conventionally hidden in file browsers and sometimes entirely gitignored. Putting user-facing documentation there means it can fail to ship with the project, or users discovering the repo never see it.
2. The filename "DOCS.md" is generic; "SPEC.md" more accurately describes the role (canon...

> *This was generated by AI during triage.*

## Triage Notes

### Diagnosis (repo state as of 2026-05-24)

- Request introduces a new command surface (`/gsd-new-ddd`) and a distinct planning mode, so this is a **feature request** (not a small enhancement).
- Scope impacts command discovery/help, initialization workflow, and roadmapper derivation semantics.
- Reporter supplied concrete structure, phased scope, and explicit follow-ups; proposal quality is high.

### Research Sweep (Context7 + repo impact)

- `Node.js` docs (`/nodejs/node` v22 series) and `Vitest` docs indicate no blocking runtime API requirement for this feature itself; this is primarily workflow/prompt orchestration.
- No external vendor API integration is required for the minimal sketch; implementation risk is internal consistency across command/workflow/agent artifacts.
- Main risk area is long-term compatibility with existing REQUIREMENTS/ROADMAP assumptions, not runtime execution.

### Recommendation

- Category: `f...

Cherry-pick references and the most surgical diff inline.

## Source commit

All v2.44.0 file additions and edits: https://github.com/jnuyens/gsd-plugin/commit/d7e4c6f

The two new files are too large to inline usefully here:

- `skills/new-ddd/SKILL.md` (75 lines) at https://github.com/jnuyens/gsd-plugin/blob/master/skills/new-ddd/SKILL.md
- `workflows/new-ddd.md` (272 lines) at https://github.com/jnuyens/gsd-plugin/blob/master/workflows/new-ddd.md

The roadmapper agent edit is the smallest surface change and inlined below. It is the single hinge point that makes the new mode work; the rest of the addition is workflow content that lives in its own files.

## Diff for `get-shit-done/agents/gsd-roadmapper.md`

Two changes: spawned-by list update at the top, and a new `` block before ``.

```diff
@@ section, ~line 17 region
You are spawned by:

-- `/gsd:new-project` orchestrator (unified project initialization)
+- `/gsd-new-project` orchestrator (u...

## User workaround: nesting script + command stubs

I hit this on a Windows global install (v1.0.0) — 71 top-level skill directories, 31 descriptions dropped every session. Wrote a bash script that applies the fix described in this issue and survives `gsd-update`:

### What it does

1. **Moves ~61 concrete `gsd-*` skills** into their namespace router's `skills/` subdirectory (strips the `gsd-` prefix)
2. **Appends a `## Sub-skills` table** to each router's `SKILL.md` so the model knows nested skills exist
3. **Creates thin command stub files** in `~/.claude/commands/` (~100 bytes each) so `/gsd-*` slash commands still register with the harness

After running: top-level drops from 71 → 10 (6 routers + 4 non-GSD skills). Zero descriptions dropped.

### Mapping used

```
gsd-ns-workflow: discuss-phase plan-phase execute-phase validate-phase verify-work phase progress pause-work resume-work fast quick autonomous ultraplan-phase mvp-phase plan-review-convergence ai-integration-phase pr-bra...

Branch `feat/78-feature-vertical-mvp-slice-mode-mvp-flag` created.

```bash
git fetch origin && git checkout feat/78-feature-vertical-mvp-slice-mode-mvp-flag
```

> *This was generated by AI during triage.*

## Triage: needs maintainer review

**Category:** enhancement
**Summary:** Umbrella PRD for Vertical MVP Slice mode: the --mvp flag on plan-phase plus /gsd mvp-phase command enabling SPIDR-based slicing, TDD gates, UAT framing, and progress visualization for solo developers building MVPs.
**Decision needed from maintainer:** scope, priority, sequencing relative to in-flight work.

> *This was generated by AI during triage.*

## Triage: needs maintainer review

**Category:** enhancement
**Summary:** Complete the namespace meta-skill architecture by actually suppressing flat skill listing when namespace router skills are installed, fulfilling the intent of the v1.40 layout that shipped the gsd-ns-* routers without relocating the ~65 concrete skills.
**Decision needed from maintainer:** scope, priority, sequencing relative to in-flight work.

Branch `feat/107-chore-roll-out-branch-protection-3-pr-pl` created.

```bash
git fetch origin && git checkout feat/107-chore-roll-out-branch-protection-3-pr-pl
```

> *This was generated by AI during triage.*

## Triage: needs maintainer review

**Category:** enhancement
**Summary:** Branch protection rollout (3-PR plan) — PR-1 through PR-3 all merged; currently in a 1-week evaluation/observation window before PR-4 flips rulesets to enforcement=active.
**Decision needed from maintainer:** scope, priority, sequencing relative to in-flight work. Specifically: confirm whether the observation window has passed without false-positive blocks and whether to proceed to PR-4 (enforcement activation).

> *This was generated by AI during triage.*

## Triage: needs maintainer review

**Category:** enhancement
**Summary:** Add ADR-0011 documenting the Runtime Install Policy Module boundary — install policy projects pure runtime install plans; runtime-specific adapters execute concrete file mutations and render format-specific config.
**Decision needed from maintainer:** scope, priority, sequencing relative to in-flight work.

Branch `feat/100-tracking-docs-readme-add-prerequisites-s` created.

```bash
git fetch origin && git checkout feat/100-tracking-docs-readme-add-prerequisites-s
```

> *This was generated by AI during triage.*

## Triage: needs maintainer review

**Category:** enhancement
**Summary:** Tracking issue for contributor PR adding prerequisites/install-verification docs — awaiting @okwn to re-open against the new repo.
**Decision needed from maintainer:** scope, priority, sequencing relative to in-flight work.

> *This was generated by AI during triage.*

## Triage: needs maintainer review

**Category:** enhancement
**Summary:** Tracking issue for contributor PR adding prerequisites/install-verification docs — awaiting contributor (@okwn) to re-open against the new repo.
**Decision needed from maintainer:** scope, priority, sequencing relative to in-flight work.

PR-3 (#112) merged + rulesets re-synced. Live ruleset context names now match the GitHub Actions matrix output (`test (, )`).

1-week evaluate observation window starts now. Monitor with:

\`\`\`
gh api repos/GSD-redux/get-shit-done-redux/rulesets/16752567/rule-suites \
--jq '.[] | {result, pr_number, evaluation_result, pushed_at}'
\`\`\`

PR-4 (flip to enforcement=active) targeted for ~1 week from now, contingent on no false-positive blocks in the telemetry.