idea-to-code

Plugin idea-to-code from marketplace idea-to-code-marketplace in humansintheloop-dev/humansintheloop-dev-workflow-and-tools. Commands read from the repo's manifest — today.

Skills (24)

• apply-design-patterns

  Consult the design pattern catalog before implementing or refactoring code.

• ask-a-friend

  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.

• brainstorm-idea

  Use when refining an idea in an idea directory through questions and answers and classifying it.

• commit-guidelines

  Provides a pre-commit checklist and commit message formatting standards for this project. Claude should use this skill when creating git commits to ensure messages follow project conventions, including proper co-authorship attribution and concise formatting.

• create-plan

  Use when creating a steel-thread implementation plan for an idea from its idea, discussion and spec files.

• debugging-ci-failures

  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.

• dockerfile-guidelines

  Provides Dockerfile best practices for this project. Claude should use this skill when creating or modifying Dockerfiles to ensure optimal layer caching by ordering instructions from most stable to least stable.

• file-organization

  Guidelines for file operations like moving, renaming, and reorganizing files. Claude should use this skill when reorganizing code structure to prefer efficient shell commands over write/delete patterns.

• find-usage

  Find all production code locations where a class, function, or method is defined and used. Use when the user asks where something is defined, instantiated, invoked, or called in production code.

• git-conflict-resolution

  Guidelines for resolving git merge and rebase conflicts efficiently. Claude should use this skill when resolving merge conflicts or rebase conflicts to prefer bulk git strategies over manual conflict marker editing.

• github-actions-gradle-cache

  Diagnose and fix stale Gradle dependency caches in GitHub Actions by deleting the setup-gradle gradle-home caches. Claude should use this skill when a Gradle build in GitHub Actions cannot resolve a SNAPSHOT dependency, or resolves an outdated SNAPSHOT, that resolves correctly locally.

• github-workflow-gradle-template

  Provides a GitHub Actions CI workflow template for Gradle/Java projects. Claude should use this skill when creating or updating CI workflows to ensure current action versions and best practices are followed.

• idea-organization

  Use when reading, creating or locating files in an idea directory under docs/ideas/, or when determining or recording an idea's type.

• incremental-development

  Guidelines for incremental development practices. Claude should use this skill when writing multiple similar files (tests, classes, configurations) to ensure each piece is verified before moving to the next.

• plan-file-management

  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-task, get-summary, list-threads). Claude MUST use this

• plan-format

  Use when writing, revising or repairing an implementation plan file (<name>-plan.md).

• plan-tracking

  Guidelines for working with plan files. Claude should use this skill when the user provides a plan file (e.g., *-plan.md) to ensure task completion is tracked in the plan file itself, not just internally.

• tdd

  a workflow for practicing Test-Driven Development (TDD)

• test-output-to-logfile

  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, and also when waiti

• test-runner-java-gradle

  a definition of tests and testing in a Java project using Gradle and JUnit 5. Advice on using Gradle to run tests.

• test-scripts-and-infrastructure

  how to structure and write tests (shell) scripts involving infrastructure

• write-design-pattern

  Write a design pattern catalog entry. Use when the user asks to document a design pattern, add a pattern to the catalog, or after a refactoring session identifies a reusable pattern.

• write-idea

  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.

• write-spec

  Use when creating or changing the specification (<name>-spec.md) of an idea.

Slash commands (2)

• /idea-to-code:claude-issue-report

  Capture mistake or improvement opportunity with 5 whys analysis

• /idea-to-code:review-design-doc

  Walk through a design document's decisions, risks, and open questions one at a time, updating the document on request

Hooks (7)

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/enforce-bash-conventions.js

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/session-recorder.js

• PermissionRequest

  node ${CLAUDE_PLUGIN_ROOT}/hooks/session-recorder.js

• UserPromptSubmit

  node ${CLAUDE_PLUGIN_ROOT}/hooks/session-recorder.js

• PostToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/session-recorder.js

• PostToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/issue-session-tagger.js

• Stop

  node ${CLAUDE_PLUGIN_ROOT}/hooks/session-recorder.js

Similar plugins