← Back to AI Insights
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
Documentation-Driven Development (DDD) /gsd-new-project /gsd-new-ddd requirements-as-list user-facing-docs-as-spec REQUIREMENTS.md REQ-ID clusters agent topology

Raw Developer Origin & Technical Request

Source Icon 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

No active discussions extracted for this entry yet.

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
trek-e • May 22, 2026
PR-1 merged. Rulesets applied in evaluate mode: - main-protection (id: 16752567) — enforcement: evaluate - release-branches (id: 16752568) — enforcement: evaluate - tag-immutability (id: 16752570) ...
trek-e • May 22, 2026
Reopening — closed in error when merged. PR-3 (re-sync rulesets with corrected context names) and PR-4 (flip to active) still pending.
trek-e • May 22, 2026
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
github-actions[bot] • May 22, 2026
Branch `feat/58-add-runtime-install-policy-adr` created. ```bash git fetch origin && git checkout feat/58-add-runtime-install-policy-adr ```
github-actions[bot] • May 22, 2026
Branch `docs/58-add-runtime-install-policy-adr` created. ```bash git fetch origin && git checkout docs/58-add-runtime-install-policy-adr ```
github-actions[bot] • May 22, 2026
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.
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.
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..

What is the technical positioning of Documentation-Driven Development (DDD) mode for project initialization.?
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.
Are engineers actively discussing 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

4
Replies
open
Issue Status

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.