gsd-autonomous
GitHub自动执行GSD工作流剩余阶段，支持讨论、规划与执行。负责将AskUserQuestion和Task映射至Codex接口，处理用户输入交互及子代理调度，确保在获得明确授权前不生成工件。
Trigger Scenarios
Install
npx skills add NeverSight/learn-skills.dev --skill gsd-autonomous -g -y
SKILL.md
Frontmatter
{
"name": "gsd-autonomous",
"metadata": {
"short-description": "Run all remaining phases autonomously — discuss→plan→execute per phase"
},
"description": "Run all remaining phases autonomously — discuss→plan→execute per phase"
}
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-autonomous. - Treat all user text after
$gsd-autonomousas{{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→headerquestion→question- Options formatted as
"Label" — description→{label: "Label", description: "description"} - Generate
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
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_inputis rejected or unavailable, you MUST stop and present the questions as a plain-text numbered list, then wait for the user's reply. Do NOT pick a default and continue (#3018). - You may only proceed without a user answer when one of these is true:
(a) the invocation included an explicit non-interactive flag (
--autoor--all), (b) the user has explicitly approved a specific default for this question, or (c) the workflow's documented contract says defaults are safe (e.g. autonomous lifecycle paths). - Do NOT write workflow artifacts (CONTEXT.md, DISCUSSION-LOG.md, PLAN.md, checkpoint files) until the user has answered the plain-text questions or one of (a)-(c) above applies. Surfacing the questions and waiting is the correct response — silently defaulting and writing artifacts is the #3018 failure mode.
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_agenthas no inlinemodelparameter; GSD embeds the resolved per-agent model directly into each agent's.tomlat install time somodel_overridesfrom.planning/config.jsonand~/.gsd/defaults.jsonare honored automatically by Codex's agent router.fork_context: falseby default — GSD agents load their own context via<files_to_read>blocks
Spawn restriction:
- Codex restricts
spawn_agentto 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>
Uses ROADMAP.md phase discovery and Skill() flat invocations for each phase command. After all phases complete: milestone audit → complete → cleanup.
Creates/Updates:
.planning/STATE.md— updated after each phase.planning/ROADMAP.md— progress updated after each phase- Phase artifacts — CONTEXT.md, PLANs, SUMMARYs per phase
After: Milestone is complete and cleaned up.
<execution_context> @/Users/machado/Projects/folhario/.codex/get-shit-done/workflows/autonomous.md @/Users/machado/Projects/folhario/.codex/get-shit-done/references/ui-brand.md </execution_context>
Project context, phase list, and state are resolved inside the workflow using init commands (gsd-sdk query init.milestone-op, gsd-sdk query roadmap.analyze). No upfront context loading needed.
Version History
- e0220ca Current 2026-07-05 23:35
