go

Detect GSE-One project state and propose the next activity from .gse files.

4|1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/nicolasguelfi/gensem --skill go-nicolasguelfi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go
Source: https://github.com/nicolasguelfi/gensem/tree/main/gse-one/plugin/skills/go
Command: npx skills add https://github.com/nicolasguelfi/gensem --skill go-nicolasguelfi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects the current project state and proposes the next activity within the GSE-One workflow, enabling faster governance and consistent progress across projects.

Core Features & Use Cases

  • Detects the current lifecycle stage by inspecting .gse/status.yaml, backlog, and plan, then suggests the next action.
  • Supports multiple project states: new, adopt, and existing projects; handles mode transitions and gate decisions.
  • Provides a baseline and transition plan for greenfield and adopted projects to align teams on the next steps.

Quick Start

Invoke the /gse:go command to detect the current project state and receive the next recommended activity.

Frequently Asked Questions about go

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

FAQPage Schema
How do I determine the current project state and next activity for a GSE-One managed project?

To determine the current project state and next activity, the orchestrator reads .gse/status.yaml, .gse/backlog.yaml, and .gse/plan.yaml to detect the lifecycle stage and suggest the next action. This enables faster governance and consistent progress across projects.

What project modes does the GSE-One workflow orchestrator support for state transitions?

The GSE-One workflow orchestrator supports adopt, micro, lightweight, and full project modes. It handles mode transitions and coordinates gating decisions to align teams on next steps for new, adopted, and existing projects.

How do I get a baseline and transition plan for an adopted project?

To get a baseline and transition plan for an adopted project, invoke the orchestrator to detect the project state and receive recommendations. It provides transition plans for greenfield and adopted projects to align teams on next steps.

Do I need .gse/plan.yaml present to coordinate gating decisions and mode transitions?

You do not need .gse/plan.yaml present to coordinate gating decisions; the orchestrator reads .gse/status.yaml and .gse/backlog.yaml alongside .gse/plan.yaml when present to propose the next activity and mode transitions.

Can I use this project state orchestrator for both new and existing projects?

You can use this project state orchestrator for new, adopted, and existing projects. It detects the current lifecycle stage by inspecting status, backlog, and plan files, then suggests the next action across all supported project states.

What's the best way to automate next-step recommendations across multiple project states?

The best way to automate next-step recommendations is to invoke the orchestrator command to detect the current project state. It inspects status, backlog, and plan files to provide gating decisions and next-step recommendations for ongoing projects.