tcx-automate

Automate Workflow

Create or update a Codex app Automation. This skill authors the scheduled task; it is not the prompt that a scheduled run should invoke.

Procedure

1. Capture the schedule, attached workspace, recurring request, desired output, and stop or notification conditions. Ask only for fields that materially affect the requested task.
2. Use $tcx-plan only when ambiguity would change scope, schedule, allowed actions, approval posture, or a stop condition. Register a clear research or monitoring request without forcing a planning interview.
3. Select the skill the future run should actually use, such as $tcx-workflow, $tcx-memory, or $tcx-server. Do not put $tcx-automate in the saved runtime prompt; that would recursively ask each run to create another automation.
4. Choose the narrowest effect level explicitly requested:
   • report-only: research, monitoring, recurring analysis, portfolio review, or status reporting; this is the default.
   • draft-order: may prepare a canonical draft order but cannot approve or submit it.
   • assisted-execution: may prepare approval and execution-ready context, then report the exact manual action required from the user.
   • turn-authorized-execution: may submit only when the saved prompt starts with the canonical plain $tcx-order-allow invocation described below.
   • turn-authorized-build: may perform workspace-local mutations only when the saved prompt starts with the canonical plain $tcx-build invocation described below. A task that changes workspace files must run with workspace-write; read-only cannot gain file-write authority, while Plan cannot issue or use the Build grant at all. Treat this as recurring delegated write intent, never as permission elevation.
   • capability-scoped-management: may manage exactly one Investment Brain or Strategy only when the saved prompt starts with $tcx-brain or $tcx-strategy. It runs in trading-research and cannot cross into Build, another managed capability, or order execution.
5. Build a compact saved prompt containing the selected runtime skill, the original recurring request and constraints, current-data or as-of rules, expected output, and explicit blocked actions. Let Head Manager choose or revise exact roles from each run's current evidence; never store a role roster, lane, or DAG.
6. Reuse a matching Codex app Scheduled Task when possible. If the Automation control is unavailable, return the schedule and ready-to-register prompt instead of creating scheduler code or raw task files.
7. Write the registration summary and future-run output instructions in the user's language unless the user asks for another language.