Agent skill
workflow-orchestration-bigdegenenergy-ai-dev-toolkit
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/workflow-orchestration-bigdegenenergy-ai-dev-toolkit
SKILL.md
Workflow Orchestration Skill
Design and execute typed, multi-step workflows with approval gates.
Overview
The Lobster workflow engine enables deterministic pipelines that:
- Execute steps in sequence with state tracking
- Pause at approval gates for human verification
- Persist state across sessions
- Handle failures gracefully
Core Concepts
Workflow Definition
A YAML file defining the pipeline:
name: feature-pipeline
description: Complete feature implementation
steps:
- name: plan
command: /plan
- name: implement
agent: "@typescript-pro"
- name: test
command: /qa
gate:
type: manual
message: "Tests pass. Continue?"
on_failure: notify
Step Types
| Type | Usage | Example |
|---|---|---|
| command | Execute a slash command | /plan, /qa, /ship |
| agent | Invoke a subagent | @code-reviewer |
| shell | Run a shell command | npm test |
| parallel | Execute steps concurrently | Multiple agents at once |
Gate Types
| Type | When to Use |
|---|---|
| manual | Critical decisions (deploy, ship) |
| timeout | Non-critical checks (auto-approve in 5m) |
| conditional | Based on previous step output |
Workflow Patterns
Pattern 1: Feature Development
name: feature-pipeline
steps:
- name: plan
command: /plan
inputs:
description: "{{ feature_description }}"
- name: implement
agent: "@typescript-pro"
inputs:
task: "Implement the plan"
- name: test
command: /qa
gate:
type: conditional
condition: "test_results.failed == 0"
- name: review
agent: "@code-reviewer"
gate:
type: manual
message: "Review complete. Ship?"
- name: ship
command: /ship
Pattern 2: Security Audit
name: security-audit
steps:
- name: scan
agent: "@security-auditor"
outputs:
- findings
- name: analyze
agent: "@zeno-analyzer"
gate:
type: conditional
condition: "findings.critical == 0"
fallback: fail
- name: report
shell: |
echo "## Security Audit Report" > report.md
# Generate report
- name: notify
command: /notify
inputs:
channel: "#security"
Pattern 3: Staged Deployment
name: deploy-pipeline
steps:
- name: build
shell: "npm run build"
- name: test
shell: "npm test"
gate:
type: conditional
condition: "exit_code == 0"
- name: deploy-staging
command: /deploy-staging
gate:
type: timeout
timeout_seconds: 300
message: "Staging deployed. Auto-continues in 5 minutes."
- name: smoke-test
agent: "@test-automator"
inputs:
environment: staging
- name: deploy-production
shell: "npm run deploy:prod"
gate:
type: manual
message: "Deploy to production?"
approvers:
- lead-developer
- devops-team
Variables and Templating
Use {{ variable }} for dynamic values:
steps:
- name: plan
command: /plan
inputs:
description: "{{ feature_description }}"
priority: "{{ priority }}"
Pass variables when starting:
/workflow feature-pipeline --var feature_description="Add OAuth" --var priority=high
State Management
Workflow state is persisted in .claude/artifacts/workflow-state/:
workflow-state/
├── feature-pipeline-abc123.json # Workflow state
├── feature-pipeline-abc123.approval.json # Pending approval
└── feature-pipeline-abc123.lock # Concurrency lock
State Fields
| Field | Description |
|---|---|
| workflow_id | Unique execution ID |
| status | Current status (RUNNING, PAUSED...) |
| current_step | Index of current/last step |
| step_results | Results of completed steps |
| pending_approval | Step waiting for approval |
| variables | Workflow variables |
Error Handling
Retry Configuration
steps:
- name: flaky-test
shell: "npm run e2e"
retry_count: 3
timeout_seconds: 300
Continue on Failure
steps:
- name: optional-lint
shell: "npm run lint"
continue_on_failure: true
Failure Actions
on_failure: notify # Send notification
on_failure: rollback # (not yet implemented)
on_failure: continue # Continue anyway
Best Practices
- Gate Critical Steps: Always add manual gates before deploy/ship
- Use Conditions: Auto-approve non-critical gates based on metrics
- Set Timeouts: Prevent workflows from hanging indefinitely
- Persist State: Let workflows resume across sessions
- Notify on Gate: Alert team when approval is needed
Integration Points
| Component | Integration |
|---|---|
/workflow |
Start a workflow |
/workflow-status |
Check progress |
/workflow-approve |
Approve pending gate |
| Gateway | Approve via Slack/Discord |
| Notifications | Alert when gates are reached |
Activation Triggers
This skill activates when prompts contain:
- "workflow", "pipeline", "orchestrat"
- "approval gate", "multi-step"
- "lobster", "typed workflow"
- "pause for approval", "wait for review"
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?