Skip to content

NEXGSD-ROADMAP.md

Latest commit

 

History

History
112 lines (78 loc) · 3.48 KB

NEXGSD-ROADMAP.md

File metadata and controls

112 lines (78 loc) · 3.48 KB

NexGSD Roadmap

Owner direction for this roadmap:

  • Brand everything clearly as NexGSD
  • Minimize confusion between old nexgsd-* and new nexgsd-*
  • Make the repo operational end-to-end
  • Make installation and machine-wide integrations reliable
  • Close legacy nexgsd-* gaps in NexGSD style, not as a raw copy

Phase 1: Brand Unification

Goal: eliminate ambiguous nexgsd-* file naming inside the repo and move to nexgsd-* naming where it improves branding and reduces confusion.

Scope:

  • Rename workflow files from nexgsd-* to nexgsd-*
  • Rename agent files from nexgsd-* to nexgsd-*
  • Rename internal config references like nexgsd-config.json to nexgsd-config.json
  • Update all mentions, links, @ references, file examples, install docs, and platform examples
  • Keep the system operational after renaming

Success criteria:

  • No broken internal file references remain
  • README, installer, workflows, agents, templates, and references all point to the new names consistently
  • The repo has one clear naming language: NexGSD

Phase 2: Workflow Surface Completion

Goal: restore missing high-value capabilities from legacy NexGSD in NexGSD's own tone and structure.

Priority additions:

  • nexgsd-map-codebase
  • nexgsd-health
  • nexgsd-update
  • nexgsd-new-milestone
  • nexgsd-complete-milestone
  • nexgsd-audit-milestone
  • nexgsd-pause-work
  • nexgsd-resume-work
  • nexgsd-add-todo
  • nexgsd-check-todos
  • nexgsd-debug
  • nexgsd-list-phase-assumptions
  • nexgsd-plan-milestone-gaps

Success criteria:

  • Missing workflows are available as repo-native workflow files
  • Existing templates that referenced missing workflows become valid again
  • The framework is stronger than legacy NexGSD on both execution and project operations

Phase 3: Documentation And Internal Consistency

Goal: make the repo readable, coherent, and trustworthy from first read to daily usage.

Scope:

  • Align README with actual repo surface
  • Fix command counts and agent counts
  • Remove stale /nexgsd- syntax where no longer valid
  • Remove stale tool-specific references that no longer match the current repo
  • Ensure templates and references do not mention nonexistent files or commands

Success criteria:

  • A new user can follow README without hitting dead ends
  • All documented commands exist
  • All documented file names exist

Phase 4: Installer And Machine-Wide Integration

Goal: make NexGSD easy to install and usable across the machine, not just in a single CLI.

Scope:

  • Verify and harden nexgsd-install.sh
  • Ensure local project install remains simple
  • Check whether a global nexgsd-install command should exist and, if so, make its setup explicit and reproducible
  • Verify update behavior against GitHub state

Success criteria:

  • Install path works cleanly in practice
  • Repo can be integrated globally without hidden manual steps
  • Update mechanism is clear, predictable, and safe

Phase 5: Validation Pass

Goal: run a repo-wide operational sanity pass after all changes.

Scope:

  • Re-scan all files for stale nexgsd-* references that should now be nexgsd-*
  • Re-check installer output and referenced paths
  • Re-check README examples against actual file names

Success criteria:

  • No obvious broken references remain
  • Repo is internally consistent
  • Brand language is unified

Immediate Execution Order

  1. Complete Phase 1 brand rename safely
  2. Fix broken references introduced by rename
  3. Restore missing workflows from Phase 2
  4. Align docs and templates
  5. Validate install and machine-wide integrations