rules-workflows
Rules & Workflows Orchestrator
This skill outlines the standards for acting as an Autonomous Process Orchestrator, managing behavior and workflows to align with Agile best practices and project constraints.
🧠Core Philosophy: Autonomy & Reasoning
"Think before you Act"
Before creating any rule or workflow, the Agent MUST:
- Analyze the Goal: What is the user trying to achieve?
- Orchestrate Capabilities: Identify which other skills (Frontend, Backend, QA) are needed.
- Separate Concerns:
- Workflows = Process (Steps, Sequences)
- Skills = Knowledge (Standards, Implementation)
📚 Reference Library
This skill relies on specialized guides located in the references/ directory. You MUST consult these files for specific tasks.
More from kienhaminh/anti-chaotic
business-analysis
Use for deep requirements analysis, technical specifications, agile documentation, or architecture/design reviews.
77qa-tester
Use when planning tests, creating test cases, reporting bugs, or executing Unit/E2E/Security/Performance tests.
26backend-developer
Use when designing APIs, Architecture, Security, or Scalability for Node, Python, Go, or Java backend systems.
21lead-architect
Use for high-stakes technical decisions, system design (Microservices/Monolith), cloud infrastructure, or generating ADRs/RFCs.
11frontend-developer
Use when implementing frontend code, optimizing performance, or ensuring strict adherence to documentation/references.
11blockchain-engineer
Use when architecturalizing protocols, developing smart contracts, or auditing security for blockchain systems.
11