Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
Brett Buddin avatar

Smith

  • 3 repo stars
  • Updated March 22, 2026
  • brettbuddin/claude-plugins

Run a research-to-plan-to-implement agent pipeline that moves a task from investigation through planning to code.

About

smith is an agent pipeline that sequences work through Research, Plan, and Implement phases. A developer uses it to drive a feature or task from initial investigation through a written plan to implemented code in a structured, repeatable flow. It is an orchestration layer for agentic development.

  • Research-plan-implement pipeline
  • Agent orchestration
  • Structured workflow

Smith by the numbers

  • Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add brettbuddin/claude-plugins
/plugin install smith@brettbuddin

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars3
Last updatedMarch 22, 2026
Repositorybrettbuddin/claude-plugins

What it does

Run a research-to-plan-to-implement agent pipeline that moves a task from investigation through planning to code.

README.md

Smith

A structured agent pipeline for Claude Code. Research a codebase, plan changes, and implement them through a human-in-the-loop workflow.

All artifacts are persisted as Markdown in a docs/ directory within the project.

Why?

I've recently revisited projects I haven't touched in years, sometimes a decade, so I'm rebuilding my understanding of the problem space from scratch right alongside Claude. Claude Code's built-in planning mode collapses research and implementation planning into one pass. For complex problems, this means by the time I see Claude's interpretation, any issues are already baked into the context window; steering everything that follows. I found myself lacking the specificity to course correct, because I hadn't completely realized my own understanding yet.

Plan quality is bounded by the quality of the context. Claude writes way better plans when the context window is already seeded with solid and agreed-upon research. Smith attempts to formalize a workflow to make this easier. The idea is to slow down the early phase where misunderstandings are cheap to fix and expensive to carry forward; especially when I need to re-learn the problem space myself before I can meaningfully guide the work. Writing is thinking and iteration is required to make a crisp thought. This workflow has helped me do that more effectively with Claude.

Install

Add the marketplace and install:

/plugin marketplace add https://github.com/brettbuddin/claude-plugins
/plugin install smith@brettbuddin

Configuration

Smith supports per-project configuration via a .smith.local.yaml file in your project root. Copy the example file as a starting point:

cp ~/.claude/plugin-commands/smith/.smith.local.example.yaml .smith.local.yaml
echo '.smith.local.yaml' >> .gitignore

All fields are optional. See the example file for available settings and their defaults.

The Workflow

Research and Discovery

Explore a topic in the codebase. The agent reads files, traces data flows, and produces a structured findings document. Annotate the document inline with corrections or questions, then revise. Repeat until the research is crisp.

flowchart LR
    R["/smith:research ‹topic›"] --> RD(["docs/research/TOPIC.md"])
    RD --> RR{"Review & Annotate"}
    RR --> RV["/smith:revise-research"] --> RD
    RR -->|Approve| Done((✓))
Command Description
/smith:research ‹topic› Research a topic in the codebase
/smith:revise-research Revise research based on inline annotations

Planning

Design an implementation approach from one or more research documents. The agent produces an ordered task checklist with specific file paths and test-first structure. Annotate the plan inline to adjust scope, ordering, or approach, then revise. Repeat until the plan is ready to execute.

As part of reviewing, you can run /smith:critique-plan to have the Critic agent evaluate the plan and add inline annotations using labeled categories: Gap, Risk, Unclear, Assumption, Ordering, Conflict, and Scope. Run /smith:revise-plan afterward to have the Planner address the annotations.

flowchart LR
    R1(["docs/research/TOPIC.md"]) --> P["/smith:plan ‹goal›"]
    R2(["docs/research/..."]) -.-> P
    P --> PD(["docs/plans/GOAL.md"])
    PD --> PR{"Review & Annotate"}
    PR -->|Revise| PV["/smith:revise-plan"] --> PD
    PR -->|Critique| CP["/smith:critique-plan"] --> PD
    PR -->|Approve| Done((✓))
Command Description
/smith:plan ‹goal› Create an implementation plan from research
/smith:critique-plan Critically review a plan, adding inline annotations
/smith:revise-plan Revise plan based on inline annotations

Socializing

Synthesize research and plans into an RFD-style document for stakeholder review. Annotate the report inline to refine framing, clarify trade-offs, or fill gaps, then revise. Repeat until it is ready to share.

flowchart LR
    RD(["docs/research/TOPIC.md"]) --> RP["/smith:report ‹topic›"]
    PD(["docs/plans/GOAL.md"]) --> RP
    RP --> RPD(["docs/reports/TOPIC.md"])
    RPD --> RPR{"Review & Annotate"}
    RPR --> RPV["/smith:revise-report"] --> RPD
    RPR -->|Approve| S["Share with Stakeholders"]
Command Description
/smith:report ‹topic› Synthesize research and plans into an RFD-style report
/smith:revise-report Revise report based on inline annotations

Execution

Execute an approved plan. The agent works through the task checklist, following a red-green-refactor cycle and validating continuously.

flowchart LR
    PD(["docs/plans/GOAL.md"]) --> I["/smith:implement"] --> C["Code Changes"]
Command Description
/smith:implement Execute the approved plan

Resources

Articles who's methodologies inspired aspects of this work.

Related skills

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.