tim-hub

Orchestrates the full powerball-harness plugin release with build, validation, version bump, CHANGELOG, tag, and GitHub Release. Use when releasing this plugin.

Generates product demo videos and release walkthroughs via Remotion. Use when creating video documentation or animated demos.

Plans and tracks tasks in .claude/harness/plans.json. Use when creating plans, adding tasks, updating markers, checking progress, or brainstorming an idea into tasks.

Initializes and configures Harness in a project — CI, memory, duo workflow, Codex. Use when setting up a new project or adding Harness configuration.

Executes plans.json tasks — solo, parallel, or breezing team mode. Use when implementing tasks or running the work loop.

Periodic housekeeping and session lifecycle management. Use when performing cleanup, pruning, or session commands.

Use when running the full team/breezing flow end-to-end — all tasks with parallel workers. Do NOT load for: single-task implementation, planning, review, release, or setup.

Use when running Plans.md tasks on a scheduled cadence (fresh context per wake-up, sprint-contract flow, plateau detection, flock guard). Do NOT load for: single-task work (harness-work), planning, review, release.

Use when the user wants to evaluate, score, review, or automatically improve an existing agent skill (a SKILL.md) — e.g. "optimize this skill", "score my skill", "review my SKILL.md", "how good is this skill", "auto-optimize", "improve skill quality". Use when a skill needs quality assessment against a rubric or iterative refinement.

Distills a session's repeatable workflow into a new project skill in .claude/skills/. Use when a session solved a non-trivial, repeatable problem and the workflow is worth capturing for reuse — e.g. "save this", "distill this", "turn this into a skill", "capture this workflow", "make a skill from this", or at the end of a session that produced a reusable pattern.

Use when the user wants to capture, replicate, or distill how a specific person (or topic/role) thinks into a reusable thinking-framework skill — e.g. "distill Munger", "make a Feynman skill", "build an X-perspective", "how does <person> think", or updating an existing <person>-perspective skill. Also use when the user expresses a vague need for a thinking partner or decision lens ("help me improve decision quality", "I need a mental-model advisor", "is there a way of thinking that helps me see business clearly").

Refines an existing project skill in .claude/skills/ with new learnings from the current session. Use when updating or improving an existing skill, or when distill-session identifies the learning extends an existing skill rather than warranting a new one — e.g. "update SKILL.md", "improve this skill", "extend this skill", "refine this skill", "tighten the skill description", or "this skill didn't trigger".

Tags the current git repository with a new version tag. Use when marking a release point in git history.

Picks the right Kubernetes Deployment update strategy (RollingUpdate / Recreate / Blue-Green / Canary) for the situation. Use when configuring a new Deployment, changing rollout config, or deciding how to ship a risky change.

Runs Multica CLI commands by mapping the user's request to the right `multica <command>` invocation. Use when the user asks to do anything with Multica — issues, agents, workspaces, autopilots, skills, squads, or the daemon.

Generates written content — blog posts, social posts, emails, and marketing copy — matched to the project's existing voice. Use when the user needs written material.

Orchestrate multiple skills through a phased workflow to solve problems, generate ideas, create plans, or build software. Use when the user asks to coordinate roles, run a full workflow, or when a task benefits from brainstorming, challenging, planning, and implementing in sequence.

Generate brainstorm ideas from multiple thinking frameworks and perspectives. Use when the user asks to brainstorm, ideate, explore options, think through a problem, generate alternatives, or needs creative input on any topic.

Aggressively challenge solutions, implementations, designs, and ideas by finding potential issues across performance, UX, security, bugs, scalability, maintainability, and edge cases. Use when the user asks to challenge, critique, stress-test, poke holes in, or review code, architecture, or ideas.

Analyze UI and UX for usability improvements across web, mobile, and CLI interfaces. Suggest and implement changes to make things easier to use and understand. Use when the user asks to review UI/UX, improve usability, simplify an interface, audit accessibility, or optimize user flows.

Create step-by-step plans for solving problems, debugging issues, building features, or architecting complex solutions. Always includes pros/cons analysis and risk consideration. Use when the user asks to plan, create a roadmap, break down a task, design an approach, outline steps, or needs a structured path forward.

Review code changes from git commit history for quality, security, and adherence to codebase patterns. Use when the user asks to review commits, review code changes, review git history, or perform a code review on recent changes.

Write unit tests for code changes across multiple stacks including JavaScript/TypeScript (Jest, Vitest), React (Testing Library), PHP (PHPUnit), Python (pytest), Django (TestCase), Hono.js, Express.js, and Flutter (Dart). Use when the user asks to write tests, add test coverage, create unit tests, or when making code changes that need test coverage. Automatically suggests tests for new or modified code.

Use when releasing a new version of this plugin — version needs bumping across package.json, manifest.json, versions.json, then tagged and pushed