菜单
Summarize the current discussion into an idea file. Use when the user asks to capture an idea, write an idea file, or after a discussion identifies a refactoring or feature worth pursuing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | write-idea |
| description | Summarize the current discussion into an idea file. Use when the user asks to capture an idea, write an idea file, or after a discussion identifies a refactoring or feature worth pursuing. |
| user-invokable | true |
Summarize the current discussion into an idea file at docs/ideas/active/<name>/<name>-idea.md.
Ask for the name — use AskUserQuestion to ask:
"What name should I use for the idea directory? (e.g., claude-runner-run)"
Suggest a kebab-case name based on the discussion topic.
Create the metadata file — docs/ideas/active/<name>/<name>-metadata.yaml with:
state: draft
Write the idea file — docs/ideas/active/<name>/<name>-idea.md with these sections:
What's wrong, duplicated, or missing. Include a short code example if the discussion involved one.
The desired end state in 1-2 sentences. This is what should change, not how to implement it.
Group by role. Use file:line references. Typical groupings:
Omit groupings that don't apply.
Guidelines for watching CI builds and diagnosing failures. Claude should use this skill when watching a CI build or investigating why a CI build failed.
Structural CRUD and reordering operations on plan files via the `i2code plan` CLI — insert/replace/delete/reorder threads and tasks, mark tasks/steps complete or incomplete, fix numbering, and query plan structure (get-next-task, get-thread, get-summary, list-threads). Claude MUST use this skill (not raw file edits) for any change to a plan file's threads, tasks, or steps, and for reading plan structure programmatically.
Consult the design pattern catalog before implementing or refactoring code.
When running test scripts or long-running commands that produce verbose output, redirect output to a log file under logs/ to avoid truncation in the Bash tool. Claude should use this skill when running test scripts, end-to-end tests, or any command likely to produce large output. NOTE: This skill does not apply to Gradle because test output is written to TEST*.xml files.
a definition of tests and testing in a Java project using Gradle and JUnit 5. Advice on using Gradle to run tests.
When stuck on a problem, formulate a well-structured question and copy it to the clipboard for pasting into ChatGPT. Claude should use this skill when debugging efforts stall or when an outside perspective would help.