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.
Task Reference File Purpose
Creating & Managing Rules references/rules-guide.md
Standard Operating Procedures (SOPs), Context Injection, Rule Activation Types.
Building Workflows references/workflows-guide.md
High-Performance Workflow Design, "Turbo" Execution, Checkpoints.
Orchestrating Skills references/orchestration-patterns.md
Skill Chaining Patterns (e.g., Spec-First, TDD), Conflict Resolution.
- Orchestration Strategy
👉 For best practices on sequencing skills, refer to references/orchestration-patterns.md .
Key principles:
-
Never Silo Skills: Code requires Architecture; Design requires Requirements.
-
Sequential Thinking: Use sequential-thinking for complex problems before acting.
-
Process vs. Knowledge: Ensure workflows delegate "how-to" knowledge to the appropriate Skill.
- Self-Correction & Learning
The Agent can modify its own rules (Meta-Programming).
-
User Correction: "Don't do X anymore" -> Trigger workflow-rule-from-feedback.md .
-
New Project: "Read this codebase" -> Trigger workflow-rule-from-codebase.md .