メニュー
Park interesting ideas for later consideration, resurface them periodically, and promote to commitments when ready.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when adding or reviewing tests for Reborn behavior — choosing a test tier, covering a bug fix, testing model/tool-choice behavior, touching tests/integration or tests/fixtures/llm_traces, or when a test needs Postgres, Docker, or a live LLM.
Navigate building a user-facing feature in the Reborn stack (a capability that crosses product_workflow → composition → webui_v2 → runtime/serve → frontend). Use when planning or implementing any new Reborn settings page, endpoint, facade method, or runtime-backed capability — especially before writing code, to avoid rebuilding what already exists and to wire it in one pass instead of layer-by-layer.
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
Generate or update the IronClaw architecture overview video using Remotion. Use when asked to update, regenerate, or modify the architecture video, add/remove scenes, or reflect codebase changes in the video.
Use when writing or reviewing a change in crates/ that adds a trait, a crate, a dependency edge, a re-export, or code in ironclaw_reborn_composition — or when deciding whether an abstraction, layer, or crate boundary is justified in the IronClaw Reborn stack.
Use when starting work in the IronClaw repo, deciding where a feature/fix/prompt/doc belongs, tracing how a request flows, looking up which crate owns a subsystem, or when repo docs, the knowledge graph, or component names seem stale, missing, or contradictory.
| name | idea-parking |
| version | 0.1.0 |
| description | Park interesting ideas for later consideration, resurface them periodically, and promote to commitments when ready. |
| activation | {"keywords":["park this","save for later","interesting idea","maybe someday","backburner","idea for later","might want to","parked ideas","idea pool","not now but","revisit later","shelve this"],"patterns":["(?i)(park|save|shelf|shelve|backburner) (this|that|the) (idea|thought|concept)","(?i)not (now|yet|ready) but","(?i)(show|list|review) parked (ideas|items)","(?i)activate (idea|parked)"],"tags":["commitments","ideas"],"max_context_tokens":1000} |
Manage ideas that are interesting but not yet actionable. Parked ideas live in projects/commitments/parked-ideas/ and are periodically resurfaced by the digest.
User says: "park this idea: do a comparison video of AWS vs GCP" or "save for later: investigate Rust WASM performance."
This skill is only successful if the parked idea is actually persisted. Do not just acknowledge or summarize an idea.
Execution order is mandatory:
memory_write for projects/commitments/parked-ideas/<slug>.mdNever say an idea was "parked", "saved for later", or "resurfaced later"
unless the corresponding memory_write succeeded.
Action:
projects/commitments/parked-ideas/<slug>.md:---
type: parked-idea
parked_at: <today YYYY-MM-DD>
source: conversation
relevance: <high|medium|low — infer from user's enthusiasm>
tags: [<relevant tags>]
---
# <Idea title>
<Description and why it is interesting.>
## Activation trigger
<What would make this worth pursuing — a condition, event, or timeframe.>
User says: "show parked ideas" or "what's on the backburner?"
Action:
memory_tree("projects/commitments/parked-ideas/", depth=1) — list all files (skip README.md)memory_read each to get title and relevanceParked ideas:
- **<title>** (parked <date>, relevance: <level>)
- **<title>** (parked <date>, relevance: <level>)
User says: "activate the comparison video idea" or "let's do the WASM performance investigation."
Action:
projects/commitments/open/ based on the idea contentUser says: "dismiss the comparison video idea" or "drop that parked idea."
Action: