goodfoot

Plugin goodfoot from marketplace goodfoot in goodfoot-io/marketplace. Commands read from the repo's manifest — 3 days ago.

Skills (12)

• ask-me

  Research a request and clarify the user's intent before acting on

• best-person

  Describe the ideal person for a task or project as a quoted persona

• documentation

  You must load this skill if you are creating or updating standalone documentation.

• instructions

  You must load this skill if you are creating or updating instructions for Claude, for example SKILL.md files.

• marketing

  You must load this skill when writing, editing, or critiquing anything that promotes a technology product to prospective or current users.

• prove-it

  Launch several subagents to critically evaluate a plan or piece of

• questions

  Walk the user through open questions one at a time, each with

• reproduce-then-resolve

  Reproduce a bug with a minimal failing test, then resolve it with

• skillify

  This skill should be used when the user asks to "skillify this", "turn this into a skill", "make a skill out of what we just did", "generalize this task into a reusable skill", or otherwise wants to capture a just-completed session task as a new skill or fold it into an existing one.

• structured-english

  Convert instructions, procedures, or algorithms into structured

• typescript-metrics

  Analyze TypeScript codebase health with metrics for complexity, coupling, duplication, cycles, data flow, and swallowed errors. Use when: (1) assessing code quality before refactoring, (2) identifying complexity hotspots, (3) finding duplicate code to extract, (4) detecting circular dependencies, (5

• worktree-cleanup

  Identify and remove git worktrees (and their branch refs) whose work has already landed in the main branch, including squash- and rebase-merged ones that naive ancestry checks miss. Use when the user says "prune merged worktrees", "clean up worktrees", "remove stale worktrees", "worktree cleanup", o

Subagents (1)

• History

  Answers questions about previous conversations, including the reasoning behind code changes, implementation decisions, and debugging context that may not be captured in commit messages. Use when investigating why something was changed, what problems led to a decision, or what was discussed before a

Hooks (1)

• PostToolUse

  node "$CLAUDE_PLUGIN_ROOT"/hooks/bin/post-tool-use.mjs

Similar plugins