AGENT SKILL

gsd-phase

CRUD for phases in ROADMAP.md — add, insert, remove, or edit phases

License 许可
Apache-2.0
所属仓库
tamarillo-ai/theta
最近更新
2026-07-15
Stars
★ 15
Forks
1

01 前言 Front Matter

name
gsd-phase
metadata
{ "short-description": "CRUD for phases in ROADMAP.md — add, insert, remove, or edit phases" }
description
CRUD for phases in ROADMAP.md — add, insert, remove, or edit phases

03 SKILL.md 正文

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-phase.
  • Treat all user text after $gsd-phase as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • header → header
  • question → question
  • Options formatted as "Label" — description → {label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y") → spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit. spawn_agent has no inline model parameter; GSD embeds the resolved per-agent model directly into each agent's .toml at install time so model_overrides from .planning/config.json and ~/.gsd/defaults.json are honored automatically by Codex's agent router.
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Spawn restriction:

  • Codex restricts spawn_agent to cases where the user has explicitly requested sub-agents. When automatic spawning is not permitted, do the work inline in the current agent rather than attempting to force a spawn.

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>

<objective> Manage phases in ROADMAP.md with a single consolidated command.

Mode routing:

  • default (no flag): Add a new integer phase to the end of the current milestone → add-phase workflow
  • --insert: Insert urgent work as a decimal phase (e.g., 72.1) between existing phases → insert-phase workflow
  • --remove: Remove a future phase and renumber subsequent phases → remove-phase workflow
  • --edit: Edit any field of an existing phase in place → edit-phase workflow </objective>

<routing>

Flag Action Workflow
(none) Add new integer phase at end of milestone add-phase
--insert Insert decimal phase (e.g., 72.1) after specified phase insert-phase
--remove Remove future phase, renumber subsequent remove-phase
--edit Edit fields of existing phase in place edit-phase

</routing>

<execution_context> @C:/Users/simon/Documents/GitHub/scrimflow/.codex/get-shit-done/workflows/add-phase.md @C:/Users/simon/Documents/GitHub/scrimflow/.codex/get-shit-done/workflows/insert-phase.md @C:/Users/simon/Documents/GitHub/scrimflow/.codex/get-shit-done/workflows/remove-phase.md @C:/Users/simon/Documents/GitHub/scrimflow/.codex/get-shit-done/workflows/edit-phase.md </execution_context>

<context> Arguments: {{GSD_ARGS}}

Parse the first token of {{GSD_ARGS}}:

  • If it is --insert: strip the flag, pass remainder (format: <after-phase-number> <description>) to insert-phase workflow
  • If it is --remove: strip the flag, pass remainder (phase number) to remove-phase workflow
  • If it is --edit: strip the flag, pass remainder (phase-number [--force]) to edit-phase workflow
  • Otherwise: pass all of {{GSD_ARGS}} (phase description) to add-phase workflow

Roadmap and state are resolved in-workflow via init phase-op and targeted reads. </context>

<process>

  1. Parse the leading flag (if any) from {{GSD_ARGS}}.
  2. Load and execute the appropriate workflow end-to-end based on the routing table above.
  3. Preserve all validation gates from the target workflow. </process>

04 同仓库更多 Skills