Jeremy edf9d0be6f docs: add GitBook-ready user-facing documentation

33 markdown files organized for GitBook import with SUMMARY.md navigation.
Covers installation, core concepts, auto mode, configuration, all providers,
cost management, skills, parallel orchestration, remote questions, teams,
headless CI, and full command reference. User-facing only — no internal/dev content.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-11 10:34:07 -05:00

1.5 KiB

Raw Blame History

Workflow Templates

Workflow templates are pre-built patterns for common development tasks. Instead of setting up a full milestone for a quick bugfix or spike, use a template to get started immediately.

Using Templates

/gsd start              # pick from available templates
/gsd start resume       # resume an in-progress workflow

Available Templates

Template	Purpose
`bugfix`	Fix a specific bug with diagnosis and verification
`spike`	Time-boxed investigation or prototype
`feature`	Standard feature development
`hotfix`	Urgent production fix
`refactor`	Code restructuring and cleanup
`security-audit`	Security review and remediation
`dep-upgrade`	Dependency update and migration
`full-project`	Complete project from scratch

Listing and Inspecting

/gsd templates                    # list all available templates
/gsd templates info <name>        # show details for a template

Custom Workflows

Create your own workflow definitions:

/gsd workflow new                  # create a new workflow YAML
/gsd workflow run <name>           # start a workflow run
/gsd workflow list                 # list active runs
/gsd workflow validate <name>      # validate definition
/gsd workflow pause                # pause running workflow
/gsd workflow resume               # resume paused workflow

Custom workflows are defined in YAML and can specify phases, dependencies, and configuration for each step.

1.5 KiB Raw Blame History