agentleFS
Sign inStart free
adrianoanthonymma16-boopadrianoanthonymma16-boop/opencode-agents/skills/gsd-plan-phase/SKILL.md

gsd-plan-phase

Skill1 starsChanged 57 days agoMITView on GitHub

Create detailed phase plan (PLAN.md) with verification loop

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 1 is common, 0 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification.

    line 7
  2. Very specific:

    Copilot (VS Code): Use vscode_askquestions wherever this workflow calls question.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<objective> Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification.

Default flow: Research (if needed) → Plan → Verify → Done

Research-only mode (--research-phase <N>): Spawn gsd-phase-researcher for phase N, write RESEARCH.md, then exit before the planner runs. Useful for cross-phase research, doc review before committing to a planning approach, and correction-without-replanning loops where iterating on research alone is dramatically cheaper than re-spawning the planner. Replaces the deleted research-phase command (#3042).

Research-only modifiers:

  • No flag — when RESEARCH.md already exists, auto-uses it: emits a one-line notice and exits cleanly, no prompt.
  • --research — force-refresh: re-spawn the researcher unconditionally, no prompt. Bypasses the existing-RESEARCH.md auto-use path.
  • --view — view-only: print existing RESEARCH.md to stdout. Does not spawn the researcher. Cheapest mode for the correction-without-replanning loop. If no RESEARCH.md exists yet, errors with a hint to drop --view.

Orchestrator role: Parse arguments, validate phase, research domain (unless skipped), spawn gsd-planner, verify with gsd-plan-checker, iterate until pass or max iterations, present results. </objective>

<execution_context> @/home/tony/.config/opencode/gsd-core/workflows/plan-phase.md @/home/tony/.config/opencode/gsd-core/references/ui-brand.md </execution_context>

<runtime_note> Copilot (VS Code): Use vscode_askquestions wherever this workflow calls question. They are equivalent — vscode_askquestions is the VS Code Copilot implementation of the same interactive question API. Do not skip questioning steps because question appears unavailable; use vscode_askquestions instead. </runtime_note>

<context> Phase number: $ARGUMENTS (optional — when omitted, the orchestrating workflow reads ROADMAP.md and selects the next unplanned phase; `gsd-tools.cjs` itself has no auto-detect feature and requires an explicit phase number)

Flags:

  • --research — Force re-research even if RESEARCH.md exists
  • --skip-research — Skip research, go straight to planning
  • --gaps — Gap closure mode (reads VERIFICATION.md, skips research)
  • --skip-verify — Skip verification loop
  • --prd <file> — Use a PRD/acceptance criteria file instead of discuss-phase. Parses requirements into CONTEXT.md automatically. Skips discuss-phase entirely.
  • --ingest <path-or-glob> — Use one or more ADR files instead of discuss-phase. Parses locked decisions + scope fences into CONTEXT.md automatically. Skips discuss-phase entirely.
  • --ingest-format <auto|nygard|madr|narrative> — Optional ADR parser format override (auto default).
  • --reviews — Replan incorporating cross-AI review feedback from REVIEWS.md (produced by /gsd-review)
  • --text — Use plain-text numbered lists instead of TUI menus (required for /rc remote sessions)
  • --mvp — MVP enrichment on top of the default tracer-first ordering: frames the phase goal as a user story and, on Phase 1 of a new project, also emits SKELETON.md (Walking Skeleton). Vertical slicing itself is now the default (see --no-tracer); --mvp no longer turns it on. Can be persisted on a phase via **Mode:** mvp in ROADMAP.md.
  • --no-tracer — Opt out of the default tracer-first decomposition and plan horizontal layers (the legacy default). By default every plan LEADS with one production-quality end-to-end tracer slice that is verified before any expansion task.
  • --no-reversibility-gates — Suppress the human checkpoint that a one-way-door decision normally earns, for runs you intend to leave unattended. By default a decision rated one-way (undo needs a migration, breaks a published contract, or is impossible) gets a checkpoint:decision before the task implementing it. Ratings are still recorded on tasks and costly items still flagged — the flag changes what stops the run, not what the plan remembers.

Normalize phase input in step 2 before any directory lookups. </context>

<process> Execute end-to-end. Preserve all workflow gates (validation, research, planning, verification loop, routing). </process>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free