gsd-workstreams

Managing parallel workstreams involves listing, creating, and switching active workstream contexts to track concurrent milestone execution without losing progress. This Skill formats JSON output into human-readable displays and persists active selections via session variables.

Tracking parallel feature development in a CLI workflow requires executing node commands to parse subcommands and format JSON results into readable tables. You can check status, progress, and resume paused workstreams across different milestones.

Switching the active workstream for a session is done by invoking CLI commands that persist the active selection via environment or session variables. This prevents cross-session collisions and maintains context for parallel feature efforts.

Running gsd-tools node commands requires a compatible environment to execute the CLI subcommands for project management workflows. No external dependencies are listed, but the environment must support node execution and session variable persistence.

Yes, you can archive completed workstreams and resume paused parallel milestone work. The functionality allows you to create separate workstreams per feature, switch context quickly, and get a consolidated progress overview across milestones.

Parallel workstream context collisions across sessions occur when active selections are not properly persisted. This Skill resolves collisions by saving the active workstream via environment or session state to avoid cross-session context loss.