sg-plan

Generate a GSD phase plan with prior lessons and discuss-then-plan workflow.

2|Updated May 15, 2026

Search Tags:#workflow orchestration #context gathering #phase planning #gsd #lesson injection #ui detection

Ready to run

npx skills add https://github.com/gyuha/super-gsd --skill sg-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sg-plan
Source: https://github.com/gyuha/super-gsd/tree/main/.agents/skills/sg-plan
Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes fragile manual handoffs by collecting phase context and generating a coherent GSD planning deliverable, optionally injecting prior lessons first.

Core Features & Use Cases

Prior lessons injection: Automatically outputs lessons from .planning/lessons/*.md (ranked) when they exist, so the plan builds on what was learned.
Phase resolution: Determines the target phase from an explicit argument or from .planning/STATE.md (YAML frontmatter Phase value).
Two-step planning chain: Runs gsd-discuss-phase to gather context and then gsd-plan-phase to create the phase plan (when GSD is available), otherwise performs a prose fallback planning flow.
UI-aware flow branching: Detects UI-related phases and offers an optional Visual Companion brainstorming step before continuing.

Quick Start

Run the Skill with your desired phase number to generate the GSD phase plan end-to-end: /super-gsd:sg-plan 3

Frequently Asked Questions about sg-plan

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

FAQPage Schema

How do I automate context gathering and phase planning for my next workflow cycle?▼

To automate phase planning, this workflow resolves the target phase, injects ranked prior lessons from `.planning/lessons/*.md`, and coordinates a discuss-then-plan chain to generate a coherent phase planning deliverable.

How do I carry over lessons learned into a new project phase plan?▼

Carrying over lessons learned into a new phase plan is handled by automatically injecting ranked lessons from `.planning/lessons/*.md` so the workflow builds directly on prior context without manual handoffs.

Do I need a specific framework installed to generate a phase plan?▼

Generating a phase plan does not strictly require a specific framework; when GSD is available it runs a two-step planning chain, otherwise it uses a manual prose fallback to create the planning file.

What is the best way to structure a phase plan when working without the GSD framework?▼

The best way to structure a phase plan without the GSD framework is using a manual prose fallback that writes directly to `.planning/phases/NN-{slug}/NN-01-PLAN.md` to maintain planning continuity.

Can I trigger UI-specific brainstorming before generating a phase plan?▼

Triggering UI-specific brainstorming before a phase plan is supported through UI-aware flow branching, which detects UI-related phases and offers an optional Visual Companion brainstorming step before continuing.

Why does my workflow orchestration fail to read the default phase number?▼

Workflow orchestration fails to read the default phase number when `.planning/STATE.md` is missing or lacks the Phase value in its YAML frontmatter, requiring an explicit phase argument to proceed.