Agent skill
workflow-enforcer
Enforces workflow discipline across ALL projects. Ensures Claude checks for specialized agents before responding, announces skill/agent usage, and creates TodoWrite todos for multi-step tasks. Activates on every session start. Triggers: automatic on all sessions, "use the right agent", "follow workflow".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/workflow-enforcer
SKILL.md
<quick_start> Before responding to ANY request:
- Check for agent: Is there a specialized agent for this task?
- Announce: "I'm using [agent] to [action]"
- Create todos: Use TodoWrite for multi-step work
- Track: Mark
in_progress→completed
| Request | Agent |
|---|---|
| Fix bug | debugging-toolkit:debugger |
| Review code | code-documentation:code-reviewer |
| Write tests | unit-testing:test-automator |
| </quick_start> |
<success_criteria> Workflow enforcement is successful when:
- Specialized agent identified and used for every applicable task
- Agent usage announced before starting work
- TodoWrite used for all multi-step tasks (3+ steps)
- Progress tracked with in_progress and completed statuses
- No rationalizations for skipping agents ("it's simple", "just a quick fix") </success_criteria>
<mandatory_protocol> Before responding to ANY user request, complete this checklist:
- Check for specialized agent - Is there an agent for this task type?
- Announce usage - "I'm using [agent] to [action]"
- Create todos - Use TodoWrite for multi-step work
- Track progress - Mark in_progress before starting, completed after finishing
Quick Reference
| User Request | Agent to Use |
|---|---|
| Fix bug / error | debugging-toolkit:debugger |
| Review code | code-documentation:code-reviewer |
| Write tests | unit-testing:test-automator |
| Optimize performance | performance-engineer |
| Security audit | security-auditor |
| Deploy / CI/CD | deployment-engineer |
| Write docs | docs-architect |
| Refactor code | legacy-modernizer |
| Build AI feature | ai-engineer |
| Production incident | incident-responder |
For the complete 70+ agent catalog, see reference/agents-catalog.md.
How to Use
Step 1: Identify Task Type
Categorize the request:
- Debugging? → debugging agents
- Code review? → review agents
- Testing? → test automation agents
- Performance? → performance engineers
- Security? → security auditors
- Deployment? → deployment engineers
Step 2: Announce
Before starting work:
"I'm using the [agent-name] to [what you're doing]"
Examples:
- "I'm using debugging-toolkit:debugger to trace this authentication error"
- "I'm using python-development:python-pro to refactor this async code"
Step 3: Create Todos
For multi-step tasks:
- Break work into specific items
- Use TodoWrite to create the list
- Mark one as
in_progressbefore starting - Mark
completedimmediately after finishing
Step 4: Follow Agent Discipline
Each agent type has its own methodology:
- TDD agents → Write tests first
- Debugging agents → Systematic root cause analysis
- Code review agents → Follow review checklist
- Deployment agents → Follow deployment protocols
Common Rationalizations to Avoid
If you think any of these, STOP and use the appropriate agent:
- "This is simple, I don't need an agent"
- "Let me just quickly fix this"
- "I can debug this manually"
- "This doesn't need a formal review"
- "I'll skip the test for now"
The right thought: "What specialized agent should I use for this task?"
Guidelines
- This skill applies to EVERY session, EVERY project, EVERY task
- No exceptions, no rationalizations, no shortcuts
- When in doubt, check
reference/agents-catalog.md</mandatory_protocol>
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?