gsd-core

name	gsd-core
description	Official GSD Core workflow adapter for Pi in this repo. Use for issue implementation, planning, milestones, roadmap work, phase discussion/planning/execution, TDD, verification, PR preparation, connector parity planning, and any task that mentions GSD.

GSD Core for Pi

This repo uses a project-local Pi adapter for official GSD Core workflows.

First steps

Before running GSD workflows in Pi:

scripts/gsd doctor
scripts/gsd list

Before implementation/review/design work, also read .agents/agentic-delivery/references/required-skills-routing.md and load the required Go/design skills for the task. For runtime/RLM/Pi-agent work involving Podman, PostgreSQL, DragonflyDB/Redis-compatible coordination, Temporal, pm runtime, pm rlm, pm agent image, pm worker, or website architecture docs, also read .agents/agentic-delivery/references/runtime-rlm-website-integration.md.

Use the Pi slash command when interactive:

/gsd plan-phase 1 --skip-research
/gsd-map-codebase --fast
/gsd-onboard --fast

Use shell prompt generation when non-interactive or when you need reproducible evidence:

scripts/gsd prompt plan-phase 1 --skip-research
scripts/gsd prompt issue-122-rebootstrap

Required workflow for implementation work

For implementation or behavior-changing work:

1. Read the issue first.
2. Read AGENTS.md.
3. Run the relevant GSD command prompt through scripts/gsd or /gsd.
4. Create or update the GSD plan, TDD ledger, and verification checklist before production edits.
5. Capture the required Go/design skills loaded from .agents/agentic-delivery/references/required-skills-routing.md.
6. Capture red/green/refactor evidence for behavior changes.
7. Run targeted verification, then the issue's broader verification.
8. Commit coherent green checkpoints.
9. Open/update the PR with GSD evidence, required skills evidence, and Closes #N or Refs #N as appropriate.

CLI help/docs/website parity

For any CLI command, subcommand, flag, output, connector surface, or help-topic change, read .agents/agentic-delivery/references/cli-help-docs-website-parity.md and update all applicable surfaces together:

• runtime help (pm help <topic>, pm <command> --help);
• bare namespace behavior (pm connectors and similar command groups should render contextual help/subcommand summary when no action is selected);
• docs/cli/** manual pages;
• website docs under website/**;
• generated help/manual fixtures, indexes, previews, and tests;
• PR verification evidence.

Safety rules

• Never request, print, store, or summarize secrets.
• Do not add dependencies without human approval.
• Do not run credentialed connector checks unless explicitly requested.
• Do not run reverse ETL execution without plan, preview, approval, execute.
• Do not expose generic shell, generic HTTP write, or generic SQL write tools.
• Destructive/admin/elevated-scope/dependency changes are human-gated.
• For planning-only work, do not edit cmd/ or internal/.

Official provenance

The adapter is based on official docs from:

https://github.com/open-gsd/gsd-core/blob/next/docs/README.md

Use these commands to inspect the pinned upstream source:

scripts/gsd version
scripts/gsd sources plan-phase