Multi Tool Task Execution Planner

Automating complex tasks across multiple software tools often results in scope creep, failed handoffs, or unintended side effects. This skill solves the problem of "hallucinated" execution by converting raw objectives into a rigorous, evidence-backed control plan. It replaces vague checklists with implementation-ready blueprints that define exactly what happens in which tool and under what conditions.

What it does

• Step decomposition breaks down broad objectives into granular, material actions with unique identifiers.
• Dependency mapping sequences tasks using hard, soft, and evidence-based constraints to prevent race conditions.
• Tool-scope validation audits tool availability and permissions to ensure operations are within evidenced limits.
• Handoff contracting defines data validation rules and schemas for every transition between different software systems.
• Risk mitigation inserts human approval gates and checkpoints around high-consequence or irreversible actions.
• Recovery planning specifies exception rules and recovery paths, including retries, rollbacks, and escalations.

How it works

1. Submit the task objective, available tools, known permissions, and desired deadline.
2. Review the Current-State Evidence Register to identify missing permissions or tool uncertainties.
3. Execute the sequenced Waves of Work, following the specific execution states like READY_TO_PREPARE.
4. Verify completion using the observable Evidence Register rather than relying on tool logs or narrative claims.

Frameworks & tools

This skill is tool-agnostic and works with any stack including REST APIs, SaaS platforms (Shopify, Stripe, Jira), CI/CD pipelines, and local CLI utilities.

Why this beats prompting it yourself

Generic prompts often ignore the "silent failure" of cross-tool handoffs and assume permissions that do not exist. This skill enforces a strict evidence-based methodology that separates preparation from side-effecting execution, ensuring you never trigger a high-consequence action without a confirmed approval gate.

Use cases

• Coordinating customer onboarding across CRM, project management, and billing systems.
• Planning multi-stage deployment workflows with manual QA approval gates.
• Converting ad hoc internal operations into reusable, traceable runbooks.
• Scaffolding complex data migrations that require cross-tool validation and recovery paths.

Known limitations

This skill creates a plan but does not perform the API calls or tool actions itself. It requires the buyer to supply evidence of tool availability and permission levels for a fully "Ready" plan.