From idea-to-code
Summarizes discussions into structured idea files with problem, goal, and code locations. Use to capture refactoring or feature ideas for later pursuit.
npx claudepluginhub humansintheloop-dev/humansintheloop-dev-workflow-and-tools --plugin idea-to-codeThis skill uses the workspace's default tool permissions.
Summarize the current discussion into an idea file at `docs/ideas/active/<name>/<name>-idea.md`.
Interactively explores relevant codebase parts and refines feature ideas into structured design specs via clarifying questions. Use when starting new features.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
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.