Captures ideas and sets triggers to surface them during specific project milestones.
Install
mkdir -p .claude/skills/gsd-plant-seed && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12574" && unzip -o skill.zip -d .claude/skills/gsd-plant-seed && rm skill.zipInstalls to .claude/skills/gsd-plant-seed
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestoneKey capabilities
- →Capture forward-looking ideas
- →Define trigger conditions for ideas
- →Preserve the full context (WHY, WHEN to surface, breadcrumbs)
- →Create seed files in .planning/seeds/
- →Surface ideas automatically at the right milestone
How it works
The skill captures forward-looking ideas with trigger conditions and stores them as seed files, which are later consumed by the gsd-new-milestone skill.
Inputs & outputs
When to use gsd-plant-seed
- →Track feature ideas
- →Set milestone-based reminders
About this skill
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-plant-seed. - Treat all user text after
$gsd-plant-seedas{{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>
Creates: .planning/seeds/SEED-NNN-slug.md Consumed by: $gsd-new-milestone (scans seeds and presents matches) </objective>
<execution_context> @C:/ExtratorLaudos/.codex/get-shit-done/workflows/plant-seed.md </execution_context>
<process> Execute the plant-seed workflow from @C:/ExtratorLaudos/.codex/get-shit-done/workflows/plant-seed.md end-to-end. </process>When not to use it
- →When the idea is not too big for now
- →When the idea does not require trigger conditions for surfacing
Limitations
- →Requires defining trigger conditions for surfacing
- →Creates seed files in a specific directory (.planning/seeds/)
- →Consumed by gsd-new-milestone, not directly by other processes
How it compares
This skill provides a structured way to capture and resurface ideas at relevant milestones, preventing context rot compared to simple one-liners in a deferred list.
Compared to similar skills
gsd-plant-seed side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gsd-plant-seed (this skill) | 0 | 3mo | No flags | Beginner |
| notion-spec-to-implementation | 5 | 6mo | No flags | Intermediate |
| weekly | 2 | 6mo | No flags | Beginner |
| goal-tracking | 1 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by phorde
View all by phorde →You might also like
notion-spec-to-implementation
openai
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
weekly
ballred
Facilitate weekly review process with reflection, goal alignment, and planning. Create review notes, analyze past week, plan next week. Use on Sundays or whenever doing weekly planning.
goal-tracking
ballred
Track progress toward 3-year, yearly, monthly, and weekly goals. Calculate completion percentages, surface stalled goals, connect daily tasks to objectives. Use for goal reviews and progress tracking.
master-plan-manager
ananddtyagi
Safe MASTER_PLAN.md management with backup, validation, and intelligent updates. Use when updating task tracking, adding features to roadmap, or modifying project documentation.
decision-logger
alirezarezvani
Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.
retrospectives
TylerGarlick
The reflection and iterative improvement layer, managing project and session retrospectives.