Launching today
/dev for Claude Code
Claude Code as a Tech Lead with parallel Worker Agents
36 followers
Claude Code as a Tech Lead with parallel Worker Agents
36 followers
Most AI coding tools give you autocomplete. /dev gives you an engineering process. A 6-phase SOP turning Claude Code into a Tech Lead with parallel Worker Agents in isolated worktrees: PRD alignment, architecture, coding, QA, code review, and iteration. Includes conflict detection, counterexample checks, mandatory security audits, and DB migration guards. Open source, MIT.
/dev for Claude Code
Raycast
/dev for Claude Code
@chrismessina Great question! You're right that Claude Code has native subagent support — /dev builds on top of that, not replaces it.
The key difference is engineering process discipline. Native subagents are like giving junior devs tasks with no guardrails. /dev adds what a real Tech Lead would enforce:
Before coding — PRD alignment + architecture review, so agents aren't building the wrong thing.
During coding — each Worker runs in an isolated git worktree, does a 6-category counterexample self-check (null, boundary, concurrency, malicious input…), and checks for file-overlap conflicts with other open Issues.
Before merging — mandatory security audits (bandit/npm audit), structured code review with veto conditions (e.g., any direct DDL = auto-reject), and post-merge PR coordination.
Think of it as: Claude Code gives you the agents, /dev gives you the SOP that keeps them from shipping broken code. It's the difference between "write code in parallel" and "run a disciplined engineering team."
For me, the biggest win here is turning AI into something closer to a tech lead rather than just a helper. I’ve noticed I write better code when I slow down and follow a process like this.
/dev for Claude Code
@marie_williamud Thanks Marie! That's exactly the insight that inspired /dev. I kept noticing that Claude Code could write great code, but without a structured process, things would slip — no architecture phase, no review, no one catching edge cases.
The "slow down and follow a process" effect is real. The 6-phase SOP forces the kind of deliberate engineering that a good tech lead brings to a team. Glad it resonates with how you think about code quality!