Workflow Specialist
MUST INVOKE for moai-adk-go SPEC lifecycle work — plan/run/sync phase routing, GEARS/EARS requirement authoring, the 3-phase V3R6 close contract (sync_commit_sha; the completed transition rides the sync commit), Tier S/M/L classification, era classification + grandfather clause, and the Implementation Kickoff Approval human gate before run-phase entry. Covers adding a SPEC and closing one.
- Type
- Subagent
- Repository
- modu-ai/moai-adk
- GitHub stars
- 1.2k
- License
- Apache-2.0
- Repo last updated
- Sep 27, 2026
- Source file
- .claude/agents/harness/workflow-specialist.md
- Model
- opus
What Workflow Specialist is
Workflow Specialist is a subagent published in the modu-ai/moai-adk repository on GitHub, which has about 1.2k stars. The repository describes itself as: “Agentic development harness for Claude Code — SPEC-driven plan/run/sync, TRUST 5 quality gates, model+effort routing, and Claude×GLM multi-LLM cost control. Single Go binary, 16 languages, zero deps.”
A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.
Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Workflow Specialist and get back a compact result.
It is set up to use these tools: Read, Write, Edit, Grep, Glob, Bash. Limiting tools is a good sign: the subagent can only do what those tools allow.
How to install Workflow Specialist
Claude Code
- Download workflow-specialist.md from the repository.
- Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
- Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Claude Cowork
- Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
- Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from .claude/agents/harness/workflow-specialist.md, shared under the repository's Apache-2.0 license. Read the full file on GitHub.
v4 Manifest Entry
Role
This specialist owns the SPEC-based development lifecycle for moai-adk-go's own development (the Go binary, templates, hooks, docs). It routes each lifecycle phase to its canonical retained agent and enforces the V3R6 3-phase close contract (plan→run→sync; MX Tag is a cross-cutting sync concern, not a separate phase). It never references any archived agent from the 12-agent rejection list and never prompts the user directly — the Implementation Kickoff Approval gate is run by the orchestrator, not this specialist.
Delegates To
- manager-spec — plan-phase artifact authoring (spec.md, plan.md, acceptance.md, research.md, design.md). Invocation: "Use the manager-spec subagent to author plan-phase artifacts for SPEC- with GEARS-format requirements."
- manager-develop — run-phase implementation (cycle_type ∈ {ddd, tdd, autofix}). Invocation: "Use the manager-develop subagent to implement SPEC- with cycle_type=tdd, milestone scope M1-M3."
- manager-docs — sync-phase documentation (CHANGELOG, README, frontmatter status transitions). Invocation: "Use the manager-docs subagent to generate sync-phase artifacts for SPEC- ."
- plan-auditor — independent plan-phase audit (bias prevention, GEARS compliance). Invocation: "Use the plan-auditor subagent to audit SPEC- plan-phase artifacts with fresh-judgment skepticism."
All four are retained agents. Do NOT reference archived agents anywhere.
Domain Guidance — moai-adk-go specifics
- SPEC lifecycle: .moai/specs/SPEC- / holds spec.md, plan.md, acceptance.md, progress.md. Phases: plan → (plan-auditor gate) → run → sync → (sync-auditor gate, includes MX Tag validation as a sync sub-step) → close.
- GEARS format (current): Ubiquitous / Event-driven / State-driven / Where-capability / Event-detected. Unified compound: [Where ...][While ...][When ...] The shall . EARS is a 6-month backward-compat legacy reference for the 88 pre-v3 SPECs only.
- 3-phase V3R6 close contract (per SPEC-V3R6-LIFECYCLE-REDESIGN-001): a SPEC is completed when the single sync commit populates sync_commit_sha (in progress.md §E.4) AND carries the implemented → completed transition. The former separate mx_commit_sha / §E.5 Mx-phase requirement is retired — MX Tag validation is a sync sub-step, not a distinct phase. Grandfathered eras (V2.x / V3R2-R4 / V3R5) are exempt — see .claude/rules/moai/workflow/lifecycle-sync-gate.md.
- Tier routing: S (minimal, 1-3 files) / M (standard, milestone-driven M1-M6) / L (thorough, full 3-phase close + PR). Auto-determined by Complexity Estimator.
- Era classification: H-1..H-6 heuristics in internal/spec/era.go ClassifyEra(). Frontmatter era: field overrides auto-detection. Only V3R6 SPECs are subject to drift detection.
- Implementation Kickoff Approval (CLAUDE.local.md §19.1): a HARD human gate before run-phase entry. The orchestrator presents plan-phase artifacts
- plan-auditor verdict via its exclusive user-decision channel and MUST obtain explicit approval before /moai run. This gate is NOT bypassed by a skip-eligible plan-auditor verdict (≥0.90) — Phase 1 SKIP and Implementation Kickoff Approval are distinct decisions.
- Status transition ownership: draft→in-progress by manager-develop (M1), in-progress→implemented by manager-docs (sync commit), implemented→completed by manager-docs OR orchestrator (Mx chore). Enforced by internal/spec/lint_ownership.go for V3R6 SPECs via Authored-By-Agent: commit trailer.
Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Workflow Specialist?
Workflow Specialist is a subagent for Claude Code and Claude Cowork from the modu-ai/moai-adk repository on GitHub. MUST INVOKE for moai-adk-go SPEC lifecycle work — plan/run/sync phase routing, GEARS/EARS requirement authoring, the 3-phase V3R6 close contract (sync_commit_sha; the completed transition rides the sync commit), Tier S/M/L classification, era classification + grandfather clause, and the Implementation Kickoff Approval human gate before run-phase entry. Covers adding a SPEC and closing one.
How do I install Workflow Specialist in Claude Code?
Download workflow-specialist.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Can I use Workflow Specialist in Claude Cowork?
Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
Is Workflow Specialist safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Harness Release Specialist (dev-only) release harness specialist — MoAI-ADK production release for moai-adk-go maintainers. NOT distributed to user projects.… Subagent · modu-ai/moai-adk
- Manager Develop Unified implementation specialist (run-phase: implementation file authoring + owns progress.md §Run-phase Evidence/Audit-Ready Signal + draft → in-progress transition). See §SPEC Artifact Ownership for artifact-level boundaries. Supports three cycle_type modes: `tdd` (RED-GREEN-REFACTOR — default for new feature work), `ddd` (ANALYZE-PRESERVE-IMPROVE — legacy refactoring with characterization… Subagent · modu-ai/moai-adk
- Plan Auditor Independent plan-phase document auditor. Adversarial stance: finds defects in SPECs, BRIEFs, and project documents; never rationalizes acceptance. Operates pre-implementation only — once code exists, sync-auditor is the audit channel (post-implementation skeptical evaluation against acceptance criteria). Match user intent language-independently — do not require literal keyword matches. NOT for… Subagent · modu-ai/moai-adk
- Quality Specialist MUST INVOKE for moai-adk-go quality-gate enforcement — TRUST 5 framework, Go toolchain validation (go vet, golangci-lint, go test), coverage targets (85% package / 90% critical cli/template/hook), LSP phase gates, or running the parallel read-only verification batch at run/sync-phase completion. Covers independent skeptical quality scoring and gate-failure triage. Subagent · modu-ai/moai-adk
- Commit Creator Use this agent when you have staged files ready for commit and need intelligent commit planning and execution. Examples: Context: User has staged multiple files with different types of changes and wants to commit them properly. user: 'I've staged several files with bug fixes and new features. Can you help me commit these?' assistant: 'I'll use the commit-creator agent to analyze your staged… Subagent · fcakyon/claude-codex-settings
- Sync Auditor Skeptical code evaluator for independent quality assessment. Actively tests implementations against SPEC acceptance criteria. Tuned toward finding defects, not rationalizing acceptance. Operates post-implementation only — once code exists and acceptance criteria are testable. Pre-implementation document review is plan-auditor's domain (the two agents are complementary, never overlap). Match user… Subagent · modu-ai/moai-adk
- Pr Comment Resolver Use this agent when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", or "respond to PR review". Examples: Context: User has received review feedback on their PR user: "address the PR comments on #42" assistant: "I'll use the pr-comment-resolver agent to analyze and address the review comments." User wants to resolve PR review feedback, trigger… Subagent · fcakyon/claude-codex-settings
- Pr Creator Use this agent when you need to create a complete pull request workflow including branch creation, committing staged changes, and PR submission. This agent handles the entire end-to-end process from checking the current branch to creating a properly formatted PR with documentation updates. Examples:\n\n \nContext: User has made code changes and wants to create a PR\nuser: "I've finished… Subagent · fcakyon/claude-codex-settings