andurilcode/professional-orchestrator
plugins/craftwork-all/skills/professional-orchestrator/SKILL.md
Entry point for professional skills — architecture, communication, process design, ethics, and leadership. Routes to the right skill based on what the user needs. Use this when the user's goal involves a professional discipline but they haven't named a specific skill.
$ install --global
skillsauthnpx skillsauth add andurilcode/skills professional-orchestratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 8:28 AM293.6s1 file scanned
SKILL.md
- name:
- professional-orchestrator
- description:
- Entry point for professional skills — architecture, communication, process design, ethics, and leadership. Routes to the right skill based on what the user needs. Use this when the user's goal involves a professional discipline but they haven't named a specific skill.
Professional Orchestrator
This skill routes — it does not reason. Read the user's intent, match it to an entry point below, then execute that skill's SKILL.md.
Step 1 — Match the User's Intent
Read what the user wants to do and match it to the closest entry below. If ambiguous, ask one clarifying question.
| User wants to... | Start with | Then |
|---|---|---|
| Architecture & Engineering | | |
| Evaluate or choose between architectures | architecture-evaluation | → execution-planning |
| Debug a software failure systematically | debugging-methodology | → casual-inference if root cause is causal |
| Design or run an experiment | experimental-design | → casual-inference after results |
| Review code or a PR | code-review-amplifier | done |
| Find incremental improvements, tech debt, or code hygiene issues | kaizen | → execution-planning or process-design |
| Understand why code is the way it is, audit undocumented fixes | kintsugi | → knowledge-architect or technical-writing |
| Planning & Execution | | |
| Break a decision into an action plan | execution-planning | done |
| Design or improve a workflow/process | process-design | → execution-planning |
| Build a financial model or business case | financial-modeling | → argument-craft |
| Writing & Communication | | |
| Write an RFC, design doc, ADR, runbook, postmortem, one-pager, or announcement | technical-writing | → narrative-construction if storytelling needed |
| Summarize a document, article, transcript, or meeting notes | summarizer | → technical-writing or argument-craft if needed |
| Structure a recommendation or argument | argument-craft | → technical-writing to write it up |
| Tell a compelling story from analysis | narrative-construction | → presentation-craft if presenting |
| Create, structure, or improve a presentation, talk, or pitch | presentation-craft | done |
| Prepare for a negotiation | negotiation-strategy | → difficult-conversations if high stakes |
| Navigate a difficult conversation | difficult-conversations | done |
| Design a meeting or workshop | facilitation-design | done |
| People & Organizations | | |
| Map stakeholder influence and blockers | stakeholder-power-mapping | → negotiation-strategy or difficult-conversations |
| Ramp up on a new domain | learning-strategy | → topic-explainer for specific concepts |
| Understand or learn a concept, technology, or idea | topic-explainer | → technical-writing to document it |
| Ethics & Fairness | | |
| Surface moral implications of a decision | ethical-reasoning | → fairness-auditing if systemic concerns |
| Audit a system for equitable outcomes | fairness-auditing | → argument-craft to present findings |
| Determine causation vs correlation | casual-inference | done |
| Knowledge Management | | |
| Capture a decision, learning, or piece of tribal knowledge | knowledge-architect | → technical-writing if formal doc needed |
| Set up or improve a team's knowledge system | knowledge-architect | done (produces architecture) |
| Someone is leaving / joining the team | knowledge-architect | detect mode for departures, audit for joiners |
| Meta | | |
| Scan all skills to find the right one(s) for a request | skill-router | → matched skill(s) |
Step 2 — Execute
- Read
skills/[skill-name]/SKILL.md - Apply that skill's full methodology
- When the skill completes, check the "Then" column above for potential follow-ups
Step 3 — Propose Next Steps
Do NOT auto-execute the "Then" skill. Instead, propose it to the user:
Based on [what the skill produced], a natural next step would be:
→ [skill-name]: [1-sentence reason this would help]
Want me to continue with that, or is this what you needed?
If multiple follow-ups are relevant, list them as options. The user chooses — the orchestrator does not chain automatically.
Canonical Chains
Architecture decision:
architecture-evaluation → argument-craft → execution-planning
Use when making and implementing a system design choice.
Building a business case:
financial-modeling → argument-craft → execution-planning
Use when you need numbers, then narrative, then action.
Navigating organizational resistance:
stakeholder-power-mapping → negotiation-strategy → difficult-conversations
Use when people are blocking progress and you need to understand why and how to move them.
Process improvement:
process-design → execution-planning
Use when a workflow is slow or broken.
Documenting a technical decision:
architecture-evaluation → technical-writing (ADR or RFC)
Use when an architecture decision needs to be written up for review or posterity.
Ethics review:
ethical-reasoning → fairness-auditing → argument-craft
Use when a system needs moral and equity analysis, then communication of findings.
Skill Registry
| Skill | Purpose |
|-------|---------|
| architecture-evaluation | Evaluate system design decisions, produce ADRs |
| code-review-amplifier | Structured pre-scanning for human code reviewers |
| debugging-methodology | Systematic debugging: reproduce, observe, hypothesize, isolate |
| execution-planning | Decompose decisions into executable plans |
| experimental-design | Design rigorous experiments to validate assumptions |
| process-design | Design workflows using Lean and value stream analysis |
| financial-modeling | Unit economics, cost-benefit, NPV/IRR, scenario modeling |
| argument-craft | Structure recommendations into persuasive arguments |
| narrative-construction | Turn analysis into compelling stories |
| negotiation-strategy | Prepare for negotiations with BATNA, ZOPA, concession planning |
| difficult-conversations | Navigate conflict, feedback, emotionally charged discussions |
| facilitation-design | Design meetings and workshops that produce decisions |
| stakeholder-power-mapping | Map influence networks and design engagement strategies |
| ethical-reasoning | Surface moral implications using multiple ethical frameworks |
| fairness-auditing | Audit systems for equitable outcomes across groups |
| learning-strategy | Build structured plans for closing knowledge gaps |
| casual-inference | Distinguish causation from correlation |
| technical-writing | Write RFCs, design docs, ADRs, runbooks, postmortems, announcements |
| topic-explainer | Explain concepts, technologies, or ideas using the best style for the topic |
| summarizer | Summarize documents, articles, transcripts, or multi-source content |
| presentation-craft | Create presentation scripts with narrative arc, slide visuals, and speaker notes |
| kaizen | Continuous improvement audit: find waste, unevenness, and overburden in code |
| kintsugi | Repair visibility audit: find undocumented fixes and add context gold |
| skill-router | Exhaustive skill scan and composition planning for any request |
| knowledge-architect | Capture decisions, context, and learnings; design team knowledge systems |
Related Skills
andurilcode/kaizen
development
VerifiedTrustedCommunity
Apply kaizen continuous improvement philosophy to any codebase — identifying waste, unevenness, and overburden at the code level and producing small, actionable improvement opportunities. Triggers on '/kaizen', 'kaizen this codebase', 'continuous improvement audit', 'find waste in this code', 'what small improvements can we make?', 'improve this codebase incrementally', 'code health check', 'codebase hygiene', 'tech debt sweep', or any request to find incremental improvement opportunities in code. Also trigger when the user says 'clean up', 'tidy up', 'make this codebase better', or expresses frustration about code quality without wanting a full rewrite. This is NOT a code review skill for PRs or diffs — kaizen operates on the codebase as a whole or a focus area, looking for systemic improvement opportunities. Use this skill even for small codebases — the philosophy scales down gracefully.
4SKILL.mdUpdated Apr 18, 2026
andurilcode/automate
tools
VerifiedTrustedCommunity
Build automation scripts and pipelines that use coding-agent CLIs (Claude Code, Codex, Gemini CLI, GitHub Copilot CLI) in headless/non-interactive mode as the AI engine, or delegate work to cloud agents (`gh agent-task`) that open pull requests asynchronously. Use this skill whenever the user wants to write a shell script, CI job, cron task, batch processor, webhook handler, or any automation that shells out to `claude`, `codex`, `gemini`, `copilot`, or `gh agent-task` — single-turn prompts, multi-turn agentic loops, parallel fan-out across files/folders, structured JSON outputs consumed by downstream tools, or cloud-delegated tasks that produce PRs. Trigger on phrases like "script that uses Claude", "automate with Claude Code", "headless Claude", "batch process files with an LLM", "pipeline with codex exec", "gemini -p", "copilot --autopilot", "gh agent-task create", "GitHub Action that calls Claude", "cron job to review PRs", "agent loop in bash", "dispatch an agent task to open a PR", "fleet-wide agent-task across repos", or any request to integrate a coding agent CLI into an automated workflow. Also trigger when the user describes the shape of a pipeline (fan-out, map-reduce, review-then-fix, extract-then-summarize, ticket-to-PR, scheduled fleet upgrade) and AI is the engine, even if they don't name the CLI explicitly.
4SKILL.mdUpdated Apr 18, 2026
andurilcode/context-engineering-orchestrator
development
VerifiedTrustedCommunity
Entry point for context engineering work. Routes to the right skill based on what the user needs — creating instructions, debugging agent failures, building documentation, or measuring outcomes. Use this when the user's goal involves agent context but they haven't named a specific skill.
4SKILL.mdUpdated Apr 18, 2026
andurilcode/topic-explainer
documentation
VerifiedTrustedCommunity
Apply this skill whenever the user asks to have a topic, concept, technology, or idea explained to them. Triggers on phrases like 'explain X to me', 'what is X?', 'how does X work?', 'teach me about X', 'help me understand X', 'break down X', 'ELI5', 'explain like I'm five', 'give me an overview of X', 'I don't understand X', 'walk me through X', or any situation where the user wants to learn or understand something rather than produce an artifact. Also trigger when someone pastes a concept and asks for clarification, when they ask 'why' something works a certain way, or when they need a refresher on a topic they've encountered before. This skill does NOT apply to 'write documentation about X' (use technical-writing) or 'analyze X' (use reasoning skills). This skill is for when the human is the learner.
4SKILL.mdUpdated Apr 18, 2026