gsd-master

Routes project work to specialized GSD sub-skills based on current state.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/optivent/gsd-kimi-cli --skill gsd-master
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-master
Source: https://github.com/optivent/gsd-kimi-cli/tree/main/skills/gsd-master
Command: npx skills add https://github.com/optivent/gsd-kimi-cli --skill gsd-master

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordination and routing across a multi-skill GSD workflow to ensure consistent, end-to-end execution of a project lifecycle.

Core Features & Use Cases

  • Orchestrates routing to gsd-new-project, gsd-plan-phase, gsd-execute-phase, gsd-verify-work, gsd-progress, gsd-help, and gsd-quick based on project state.
  • Preserves user context between steps and enables handoffs.
  • Delegates work to specialized skills, reducing coupling and enabling parallel execution where possible.

Quick Start

Activate the GSD master flow with /flow:gsd-master to route to the appropriate skill based on your project state.

Frequently Asked Questions about gsd-master

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

FAQPage Schema
How do I orchestrate a multi-agent workflow for project management?

Multi-agent workflow orchestration routes tasks to specialized skills to execute a complete spec-driven lifecycle. This flow control layer preserves user context and spawns sub-skills for initialization, planning, execution, and verification.

What is the best way to manage an end-to-end spec-driven workflow?

Managing an end-to-end spec-driven workflow involves routing to specialized skills based on project state. A master orchestrator determines whether to initialize, plan, execute, verify, or progress, ensuring smooth handoffs and context preservation.

How do I route tasks to specialized skills for software engineering projects?

Routing tasks to specialized software engineering skills requires a lightweight flow control layer that assesses project state. It delegates work to sub-skills for new projects, planning, execution, and verification, reducing coupling and enabling parallel execution.

Can I use a multi-agent orchestrator for both new projects and quick tasks?

A multi-agent orchestrator supports new projects, existing projects, and quick tasks. It determines the appropriate project phase and routes to corresponding sub-skills, preserving user state and context throughout the workflow handoffs.

How does a workflow orchestrator preserve context between project phases?

A workflow orchestrator preserves context between project phases by acting as a lightweight flow control layer. It maintains user state and coordinates smooth handoffs between specialized sub-skills during initialization, planning, execution, and verification.

When should I not use a multi-agent routing orchestrator for project management?

You should avoid a multi-agent routing orchestrator if your project requires a tightly coupled, single-skill execution rather than spec-driven workflows. This approach reduces coupling by delegating work to specialized sub-skills, which may not suit simple, isolated tasks.