gsd-ns-manage

Manage GSD workspace lifecycles and agent-based task orchestration in Codex.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-ns-manage-nnexai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ns-manage
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-ns-manage
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-ns-manage-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of managing multi-repo workstreams, workspace lifecycles, and agent-based task execution within the GSD framework.

Core Features & Use Cases

  • Workflow Orchestration: Provides a unified interface to manage workspaces, threads, and parallel workstreams.
  • Agent Dispatch: Maps high-level GSD tasks to Codex-compatible agent spawning, including fallback logic for generic schemas.
  • Use Case: When switching between multiple active tickets, use this skill to pause current work, spin up a fresh workspace thread, and delegate sub-tasks to specialized agents without manual context switching.

Quick Start

Invoke the gsd-ns-manage skill to list all active workspaces and switch to the feature-x thread.

Frequently Asked Questions about gsd-ns-manage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate multi-repo workstreams and manage workspace lifecycles?

You orchestrate multi-repo workstreams by using agent-based task execution to manage workspace lifecycles. This maps high-level GSD workflow commands to native agent spawning, ensuring consistent execution across parallel threads.

How does agent dispatch work for task orchestration within a workspace?

Agent dispatch translates high-level GSD tasks into native agent spawning protocols. It includes fallback logic for generic schemas, mapping specialized sub-tasks to distinct agents without manual context switching.

Can I switch between active tickets and pause current work in a GSD workflow?

Yes, you can switch between active tickets by invoking workspace thread management. This pauses your current work, spins up a fresh workspace thread, and delegates sub-tasks to specialized agents.

What is the best way to handle state management for parallel workstreams?

The best way to handle state management for parallel workstreams is through schema-specific agent dispatch. This ensures consistent execution of multi-repo workstreams by maintaining state across delegated tasks.

Do I need specific schemas to use agent dispatch for GSD workflows?

No, specific schemas are not strictly required. The agent dispatch mechanism includes fallback logic for generic schemas, allowing native agent spawning to proceed even without specialized schema definitions.

Why does my GSD workflow command fail to spawn agents in the Codex environment?

GSD workflow commands may fail to spawn agents if the schema-specific dispatch encounters unsupported protocols. The system relies on native user input protocols and fallback logic to ensure consistent execution.