Agentic Workflows — Mastery5 / 8
Custom Slash Commands as Team Workflows
A custom slash command is a reusable prompt you commit to the repo — so the whole team runs the same high-quality instruction instead of re-typing it.
The best prompt your team ever wrote is worthless if everyone retypes a worse version of it. A custom slash command fixes that: it is a Markdown file whose body is a prompt, committed to the repo and run with /its-name.
The whole mechanism
Drop a file in .claude/commands/ (shared via git) or ~/.claude/commands/ (personal). The filename becomes the command:
<!-- .claude/commands/changelog.md -->
Summarize the staged git changes as a concise changelog entry,
grouped by Added / Changed / Fixed.
Now /changelog runs that prompt for everyone on the team.
Three features that make it powerful
Arguments — $ARGUMENTS for everything, or $1, $2 for positional:
Fix issue #$1 with priority $2. Find the failing test, propose a patch,
explain the root cause.
Invoke: /fix-issue 4242 high.
Frontmatter configures the command:
---
description: Conventional-commit message from staged changes
argument-hint: [scope]
allowed-tools: Bash(git diff:*), Bash(git log:*)
model: claude-haiku-4-5
---
Inline context pulls live data in: prefix a line with ! to run a shell command and embed its output, or reference a file with @src/app.ts.
Why this is a team multiplier
Commands package intent; hooks enforce rules; MCP provides tools. The last building block is delegation — handing focused work to subagents.
Series — Agentic Workflows — Mastery
- Part 01The Agentic Workflow MindsetMost developers treat AI like a smarter autocomplete. The ones who pull ahead treat it like a teammate that acts. Here is the mental model.
- Part 02MCP Servers 101 — Give Your Agent Real ToolsThe Model Context Protocol is how your agent stops guessing and starts querying your database, your issues, your browser. Here is the mental model and the first connection.
- Part 03Build Your First Custom MCP ServerOff-the-shelf servers cover GitHub and Postgres. The high-leverage one is the server only you can write — the bridge to your own system.
- Part 04Hooks — Make the Agent Obey Your RulesA prompt asks the model to remember. A hook makes it happen — deterministically, every time, outside the model's control.
- Part 05Custom Slash Commands as Team Workflows — you are hereA custom slash command is a reusable prompt you commit to the repo — so the whole team runs the same high-quality instruction instead of re-typing it.
- Part 06Subagents — Delegating Work That ScalesOne giant context gets slow and vague. Subagents let the main agent hand focused work to specialists with their own context and tools — and run them in parallel.
- Part 07The Daily-Driver Setup — Settings, Permissions, Status LineThe difference between fighting the agent and flowing with it is twenty minutes of configuration you do once. Here is the setup.
- Part 08Multi-Tool Pipelines — Ticket to Reviewed BranchThe payoff: chain MCP, hooks, commands and subagents into one flow that takes a ticket to a reviewed branch — with you in the loop only where it counts.