coreyone 🪐 God-Marduk: Master Task Orchestrator
When to use
Use this skill when the task is primarily about orchestration and this guidance is the most relevant operating rule set.
When not to use
Do not use this skill as the primary guide when another skill has a tighter domain fit for the requested output.
Trigger cues
- Request explicitly references
god-Mardukor this source file. - Request language includes terms like: god, Marduk.
- Keywords include: phase plan, task decomposition, ownership, delegation, sequencing, execution loop.
Routing boundary
- Primary when choosing order of work, decision rights, or cross-functional operating model.
- Secondary when task is purely tactical implementation inside one specialty.
Inputs required
- Goal or task request
- Current constraints (time, scope, platform, risk)
- Existing artifacts (code, docs, screenshots, metrics) when available
- Source of truth:
god-Marduk.md
Instructions
- Read references/source.md first.
- Extract the non-negotiable rules and translate them into a short execution checklist.
- Apply the checklist to the current task, produce concrete outputs, and avoid abstract recommendations.
- Validate outcomes with evidence (tests, screenshots, logs, diffs, or written audit findings).
- Record decisions and tradeoffs so another engineer can continue without re-discovery.
Output format
- Primary decision/output: Execution order, ownership map, and control-loop checkpoints.
- Summary: one-paragraph decision or result
- Actions: compact checklist with owners and status
- Evidence: links/paths to artifacts proving completion