gsd-add-backlog
Add an idea to the backlog parking lot (999.x numbering)
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-15
- Stars
- ★ 15
- Forks
- 1
01 前言 Front Matter
- name
- gsd-add-backlog
- metadata
- { "short-description": "Add an idea to the backlog parking lot (999.x numbering)" }
- description
- Add an idea to the backlog parking lot (999.x numbering)
03 SKILL.md 正文
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-add-backlog. - Treat all user text after
$gsd-add-backlogas{{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 (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 (Codex uses per-role config, not inline model selection)fork_context: falseby default — GSD agents load their own context via<files_to_read>blocks
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> Add a backlog item to the roadmap using 999.x numbering. Backlog items are unsequenced ideas that aren't ready for active planning — they live outside the normal phase sequence and accumulate context over time. </objective>
<process>
-
Read ROADMAP.md to find existing backlog entries:
cat .planning/ROADMAP.md -
Find next backlog number:
NEXT=$(node "/Users/wilderherrera/Desktop/convision/.codex/get-shit-done/bin/gsd-tools.cjs" phase next-decimal 999 --raw)If no 999.x phases exist, start at 999.1.
-
Create the phase directory:
SLUG=$(node "/Users/wilderherrera/Desktop/convision/.codex/get-shit-done/bin/gsd-tools.cjs" generate-slug "{{GSD_ARGS}}" --raw) mkdir -p ".planning/phases/${NEXT}-${SLUG}" touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep" -
Add to ROADMAP.md under a
## Backlogsection. If the section doesn't exist, create it at the end:## Backlog ### Phase {NEXT}: {description} (BACKLOG) **Goal:** [Captured for future planning] **Requirements:** TBD **Plans:** 0 plans Plans: - [ ] TBD (promote with /gsd-review-backlog when ready) -
Commit:
node "/Users/wilderherrera/Desktop/convision/.codex/get-shit-done/bin/gsd-tools.cjs" commit "docs: add backlog item ${NEXT} — ${ARGUMENTS}" --files .planning/ROADMAP.md ".planning/phases/${NEXT}-${SLUG}/.gitkeep" -
Report:
## 📋 Backlog Item Added Phase {NEXT}: {description} Directory: .planning/phases/{NEXT}-{slug}/ This item lives in the backlog parking lot. Use /gsd-discuss-phase {NEXT} to explore it further. Use /gsd-review-backlog to promote items to active milestone.
</process>
<notes>
- 999.x numbering keeps backlog items out of the active phase sequence
- Phase directories are created immediately, so /gsd-discuss-phase and /gsd-plan-phase work on them
- No
Depends on:field — backlog items are unsequenced by definition - Sparse numbering is fine (999.1, 999.3) — always uses next-decimal </notes>
04 同仓库更多 Skills
deploy-app
Deploy the application to staging or production environments.
deploy
Deploy the application to environments.
building-native-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
create-section
Use when creating a new section for the AI Workshop presentation. Guides through title slide setup, layout choices, and content gathering. Activates when user wants to add a new topic section to the slideshow.
ship-checker
Run a full pre-ship review for this repo. Use when asked if a change is ready to deploy, publish, or ship.
lint-check
Run repository linters and report failures.