🏗️ juan-workflow — Claude Code Plugin
The non-engineer's development guardrails — by Dojo Coding Labs
The Origin Story
Juan is Head of Product & Growth at Dojo Coding Labs. He's not an engineer. He's a product guy who lives in Linear, thinks in user stories, and has strong opinions about button colors.
One day Juan decided he was tired of writing PRDs and waiting. He wanted to contribute to the codebase. The engineers were... concerned.
"What if he pushes to main?"
"What if he duplicates work someone's already doing?"
"What if he skips the spike and just starts coding?"
"What if Greptile roasts him and he doesn't fix it?"
So Juan did what any self-respecting Head of Product would do: he built guardrails for himself.
The result is juan-workflow — a Claude Code plugin that enforces the full development lifecycle every single time Juan sits down to code. Spike first. Check for duplicates. Get Greptile approval. Assign a human reviewer. No shortcuts.
The engineers love it. Juan ships code now. Nothing breaks. And the workflow is so good the whole team uses it.
Open-sourced because if Juan can do it, anyone can. 🤷
What It Does
One command — /juan-workflow:juan-is-working — orchestrates your entire dev session:
Phase 0 🔍 Setup Learn your team's patterns (first run only)
Phase 1 🎯 Discovery What are we building? Assess scope.
Phase 2 🔎 Duplicates Check Linear + GitHub for existing work
Phase 3 📌 Spike Create spike in Linear, brainstorm, document
Phase 4 🏗️ Build Create task, branch, implement, lint, test
Phase 5 🚀 PR + Review Push PR, wait for Greptile, address feedback
Phase 6 👋 Handoff Assign reviewer (round-robin), update Linear
Every phase confirms before advancing. Everything is cross-linked (Linear ↔ GitHub). Nothing falls through the cracks.
Installation
# In Claude Code:
/plugin marketplace add DojoCodingLabs/juan-workflow
/plugin install juan-workflow@juan-workflow
That's it. Type /juan-workflow:juan-is-working and you're off.
Updating
# Update the marketplace catalog first:
/plugin marketplace update DojoCodingLabs/juan-workflow
# Then update the plugin:
/plugin update juan-workflow@juan-workflow
Restart your Claude Code session after updating.
Requires:
Local Development
git clone https://github.com/DojoCodingLabs/juan-workflow.git
cd juan-workflow
# In Claude Code:
/plugin marketplace add .
/plugin install juan-workflow
Usage
Every time you sit down to work:
/juan-workflow:juan-is-working
Or with a task description:
/juan-workflow:juan-is-working add a search bar to the movie list page
The workflow walks you through:
- "What do you want to work on?" — Explain your task
- Duplicate check — Makes sure nobody's already doing this
- Spike — Brainstorm back and forth, document decisions in Linear
- Implementation — Create branch, code, lint, test
- PR — Push and wait for Greptile review
- Handoff — Assign a human reviewer, update Linear
Works with /feature-dev
For large tasks, the workflow will suggest using /feature-dev for the implementation phase. It handles everything before (spike, planning) and after (PR, review, handoff) — /feature-dev handles the actual coding.
What's Inside
juan-workflow/
├── .claude-plugin/
│ ├── plugin.json # Plugin metadata
│ └── marketplace.json # Marketplace catalog
├── commands/
│ └── juan-is-working.md # 🧠 The main orchestrator (all 7 phases)
├── agents/
│ ├── pattern-learner.md # 🔍 Discovers org patterns (Phase 0)
│ └── duplicate-checker.md # 🔎 Finds overlapping work (Phase 2)
├── scripts/
│ ├── wait-greptile.sh # ⏳ Polls for Greptile review (Phase 5)
│ └── assign-reviewer.sh # 🎯 Round-robin reviewer pick (Phase 6)
├── LICENSE
└── README.md
Pattern Learning (Phase 0)
