Install
$ agentstack add skill-joaquimscosta-arkhe-claude-plugins-workflow-orchestration ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Workflow Orchestration
Guide users through structured thinking and recommend appropriate tools for complex tasks.
Quick Decision
| Situation | Recommendation | |-----------|----------------| | Multi-step project, full SDLC | /core:develop command | | Plan only, implement later | /core:develop --plan-only | | Resume existing plan | /core:develop @path/to/plan.md | | Single complex problem needing deep analysis | /think command | | Security-sensitive or high-stakes work | /core:develop --validate | | Strategic decision with long-term impact | deep-think-partner agent | | Simple task, clear steps | Inline guidance (no command needed) |
When to Orchestrate
Detect these signals for structured thinking:
Keyword triggers:
- "workflow", "orchestration", "coordinate", "parallel"
- "multi-step", "sequential", "dependencies"
- "break down", "plan this out", "how should I approach"
Context triggers:
- Architectural decisions affecting multiple components
- Multi-file changes requiring coordination
- Problems with unclear scope needing discovery
- Tasks that benefit from specialist agents
Orchestration Pattern
When structured approach is needed:
1. GATE → Is the request clear and actionable?
2. CONTEXT → What files/patterns are relevant?
3. PLAN → What tasks? Parallel vs sequential?
4. EXECUTE → Deploy specialists, maximize parallelism
5. VALIDATE → Confidence scoring (if needed)
6. REPORT → Summary with next steps
Command Reference
/core:develop [flags]
Unified SDLC command with 6-phase pipeline and multi-agent orchestration.
Flags:
--plan-only- Stop after Phase 2 (save plan, don't implement)--validate- Enable deep validation with opus agent--phase=N- Execute specific phase only--auto- Autonomous mode (no checkpoints)
Best for: Feature implementations, refactoring projects, any multi-step development task.
Resume mode: /core:develop @path/to/plan.md loads existing plan and continues.
/think [problem]
Invoke deep-think-partner for collaborative reasoning.
Best for: Single complex problems, decision analysis, reasoning validation, architectural decisions.
Inline Guidance
For simpler tasks, provide structured thinking directly:
- Clarify scope - What exactly needs to be done?
- Identify dependencies - What must happen first?
- Plan sequence - Parallel where possible, sequential where required
- Execute - Work through each step
- Verify - Check results meet requirements
Model Tier Strategy
| Task Type | Model | Use Case | |-----------|-------|----------| | Gating, routing | haiku | Quick decisions, simple queries | | Implementation | sonnet | Standard coding, documentation | | Deep analysis | opus | Architecture, complex reasoning |
Output
When providing orchestration guidance:
## Recommended Approach
**Complexity:** [Low | Medium | High]
**Suggested tool:** [command or inline]
### Why
[Brief explanation of why this approach fits]
### Steps
1. [First step]
2. [Second step]
...
Additional Resources
- [WORKFLOW.md](WORKFLOW.md) - Detailed orchestration patterns
- [EXAMPLES.md](EXAMPLES.md) - Real-world usage scenarios
- [TROUBLESHOOTING.md](TROUBLESHOOTING.md) - Common issues and solutions
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: joaquimscosta
- Source: joaquimscosta/arkhe-claude-plugins
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.