SaaS Metrics
Gemini Executive Synthesis
Documentation-Driven Development (DDD) mode for project initialization.
Technical Positioning
Expanding project initialization methodologies to support documentation as the primary specification artifact, alongside existing requirements-driven approaches.
SaaS Insight & Market Implications
This proposal introduces a significant strategic shift: Documentation-Driven Development (DDD) as a first-class project initialization mode. It acknowledges that for specific product types (CLIs, SDKs, APIs), user-facing documentation serves as the de facto specification, rendering traditional `REQUIREMENTS.md` less effective. This enhancement directly addresses a workflow mismatch for developers building public-facing interfaces, aiming to reduce friction and improve alignment between design and implementation. By offering a parallel `/gsd-new-ddd` command, the platform positions itself to cater to a broader range of development paradigms, enhancing its utility for projects where API contracts and user guides are paramount. This is a strategic move to capture more diverse developer workflows.
Proprietary Technical Taxonomy
Raw Developer Origin & Technical Request
GitHub Issue
May 24, 2026
Repo: open-gsd/get-shit-done-redux
Documentation-Driven Development (DDD) mode as a sibling to /gsd-new-project
### Pre-submission checklist
- [x] I have confirmed this improves existing behavior. It does not add a new command, workflow, or concept.
Note: this proposal does add a new top-level command (`/gsd-new-ddd`) and a new mental model (DDD mode). I am filing as enhancement rather than feature because the new command is a sibling to the existing `/gsd-new-project` (same shape, same downstream artifacts, same agent topology). Happy to switch to the feature template if the maintainer prefers.
- [x] I have searched existing issues and this enhancement has not already been proposed.
- [x] I have read CONTRIBUTING.md and understand I must wait for `approved-enhancement` before writing any code.
- [x] I can clearly describe the concrete benefit, not just "it would be nicer".
### What existing feature or behavior does this improve?
Project initialization. Currently `/gsd-new-project` is the sole entry point. It produces REQUIREMENTS.md as the user-validated spec, then derives phases from REQ-ID clusters.
For a meaningful class of projects (CLIs, libraries, SDKs, APIs, plugin systems), the user-facing surface IS the spec, and requirements-as-list is a less natural primary artifact than user-facing-docs-as-spec. This proposal adds Documentation-Driven Development (DDD) as a parallel mode.
### Current behavior
`/gsd-new-project` flow:
1. Questioning
2. Research (optional, parallel)
3. REQUIREMENTS.md generation (REQ-IDs, acceptance criteria, traceability table)
4. User validates RE...
Developer Debate & Comments
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...
> *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...
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 (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...
@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
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from open-gsd/get-shit-done-redux.
Extracted Positioning
Implementation of branch protection rulesets for repository security and integrity.
Establishing robust CI/CD pipeline security, code quality, and governance through enforced branch protection.
Top Replies
PR-1 merged. Rulesets applied in evaluate mode: - main-protection (id: 16752567) — enforcement: evaluate - release-branches (id: 16752568) — enforcement: evaluate - tag-immutability (id: 16752570) ...
Reopening — closed in error when merged. PR-3 (re-sync rulesets with corrected context names) and PR-4 (flip to active) still pending.
PR-3 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 rep...
Extracted Positioning
Documentation of the Runtime Install Policy Module boundary via an Architectural Decision Record (ADR).
Formalizing architectural decisions to ensure clarity, maintainability, and clear ownership boundaries for runtime installation processes.
Top Replies
Branch `feat/58-add-runtime-install-policy-adr` created. ```bash git fetch origin && git checkout feat/58-add-runtime-install-policy-adr ```
Branch `docs/58-add-runtime-install-policy-adr` created. ```bash git fetch origin && git checkout docs/58-add-runtime-install-policy-adr ```
Branch `chore/58-add-runtime-install-policy-adr` created. ```bash git fetch origin && git checkout chore/58-add-runtime-install-policy-adr ```
Extracted Positioning
Completion of the namespace meta-skill architecture to suppress flat skill listings in the system prompt.
Optimizing AI model context window usage and improving skill discoverability by reducing prompt clutter.
Top Replies
Branch `feat/69-enh-complete-the-namespace-meta-skill-ar` created. ```bash git fetch origin && git checkout feat/69-enh-complete-the-namespace-meta-skill-ar ```
> *This was generated by AI during triage.* ## Triage: needs maintainer review **Category:** enhancement **Summary:** Complete the namespace meta-skill architecture by actually suppressing flat ski...
## 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 ...
Extracted Positioning
Vertical MVP Slice mode for project planning and execution.
Shifting from horizontal (layer-by-layer) to vertical (end-to-end feature) planning to enable earlier validation and reduce architectural risk for solo developers using AI coding tools.
Top Replies
Branch `docs/78-feature-vertical-mvp-slice-mode-mvp-flag` created. ```bash git fetch origin && git checkout docs/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 /gs...
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 ```
Extracted Positioning
Bug fixes for `gsd-sdk query milestone.complete` output generation, specifically `MILESTONES.md` accuracy.
Ensuring data integrity and accurate reporting for project milestones and roadmap tracking.
Frequently Asked Questions
Market intelligence mapped to Documentation-Driven Development (DDD) mode for project initialization..
How is Documentation-Driven Development (DDD) mode for project initialization. positioned in the market?
Based on our AI analysis of the original developer request, its primary technical positioning is: Expanding project initialization methodologies to support documentation as the primary specification artifact, alongside existing requirements-driven approaches.
How is the developer community reacting to Documentation-Driven Development (DDD) mode for project initialization.?
Yes, we have tracked 4 direct responses and active debates regarding this specific topic originating from GitHub Issue.
Which technical concepts are associated with Documentation-Driven Development (DDD) mode for project initialization.?
Our proprietary extraction maps Documentation-Driven Development (DDD) mode for project initialization. to adjacent architectural concepts including Documentation-Driven Development (DDD), /gsd-new-project, /gsd-new-ddd, requirements-as-list.
Engagement Signals
Cross-Market Term Frequency
Quantifies the cross-market adoption of foundational terms like Documentation-Driven Development (DDD) and /gsd-new-project by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.