AaronZHAO84/codex-skills

TaskOrch

TaskOrch is the entry and coordination layer for tasks of any size. Superpowers remains the primary orchestration and execution core; Murpick is an optional, user-friendly intake and selection aid.

Workflow

1. Detect the goal, constraints, requested output path, and whether the task is simple, medium, or complex.
2. Choose the smallest sufficient route: direct single-Skill execution for simple work; the existing Superpowers workflow for multi-step work.
3. Offer Murpick-assisted intake when it improves boundary definition, candidate selection, or confirmation. Otherwise use direct intake. Do not invoke Murpick merely for ceremony.
4. If Murpick is used, treat selections and non-selections as scope decisions. Do not let it replace Superpowers' spec or plan.
5. Invoke the appropriate Superpowers Skill(s) in their natural order. Preserve Superpowers' spec, plan, implementation, testing, debugging, review, and verification outputs. Do not add a second plan or a second verification process.
6. At genuine decision points only, present concise HTML confirmation content. Do not pause for routine low-risk steps already covered by an approved plan.
7. Keep Markdown source records of inputs, decisions, Skill names, stage changes, outputs, evidence, blockers, and confirmations. Generate HTML views for anything the user needs to inspect.
8. If an output path is specified, create only the directory structure justified by complexity. For a simple task use spec, plan, execution, and verification; add intake, decisions, artifacts, or delivery folders only when needed.
9. Report status as not started, in progress, awaiting confirmation, complete, partial, skipped, or blocked. Never claim completion without verification evidence.

Prompt contract

Use TaskOrch for this task. First classify its complexity and choose the smallest sufficient workflow. Use Superpowers as the main execution process. Use Murpick only if it improves scope or option selection. Preserve Superpowers' spec and plan; do not duplicate its later phases. Report selected Skills, current stage, decisions, evidence, blockers, and completion status. Show user-facing reports as HTML and keep Markdown records.

When strict transparency is requested, report exact Skill names and namespaces before execution and at each genuine stage transition. A user-cancelled Skill stays disabled unless explicitly re-enabled.

Boundaries

• Murpick selects and clarifies; Superpowers plans and executes.
• TaskOrch coordinates and presents; it does not replace either tool.
• spec and plan remain mandatory artifacts for Superpowers-led work, but may be concise for a small task.
• Do not create a full Murpick menu for a trivial task.
• Do not run parallel work unless tasks are genuinely independent.
• Do not duplicate brainstorming, planning, testing, debugging, review, or verification already performed by Superpowers.

Records

Use Markdown as the durable source of truth. Use HTML for user-facing intake, confirmations, progress, and delivery reports. Preserve prior records instead of silently overwriting major revisions.