Stage Launch
When to use
Use this skill for stage launch when you need to prepare a managed agent for a controlled first launch. The expected result is a launch checklist with rollback and owner.
Boundaries
Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it.
Inputs
Inspect the approved build brief, account access, tool scopes, and test environment. Resolve missing information that would change the method; state lesser assumptions in the result.
Method
- Diagnose. Draw the path from user request to tool call to external effect. List the account owner, tool permissions, data stores, rate limits, and actions that cannot be undone.
- Decide. Stage configuration before the live action and separate reversible from irreversible steps.
- Produce. Build a launch checklist with rollback and owner from the inspected material; keep assumptions distinguishable from observed facts.
Decision rules
- Gate launch on a bounded task, a measurable success condition, an explicit stop rule, and a fallback for missing context or tool failure. Keep the first run supervised.
- When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact.
Domain rules
- Set tool permissions, spending limits, and a human-owned stop condition before launch.
- Evaluate a complete task and a failed run before allowing recurring execution.
Verification
Confirm permissions, cost bounds, and a first-run acceptance case. Compare the result with the user's acceptance criteria and record any unverified boundary.
Record an example task, the agent trace, expected result, actual result, cost, and the human decision required before recurring execution.
Approval and stop conditions
- Before recurring or external actions, identify the owner, tool permissions, spending limit, approval gate, and disable path.
- Stop when the agent cannot determine whether an action succeeded, reaches its retry or budget limit, or would exceed an agreed boundary.
- Pilot with human review before scheduling unattended execution. Report unresolved failures and who can disable the workflow.
Stop conditions
If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed.
Output
Provide a launch checklist with rollback and owner. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use.
