メニュー
Create or change a recurring market review, alert, or bounded position-management Routine and its optional Mandate. Use when the user asks the agent to remember work on a cadence, monitor a condition, send an alert, or manage a position until a condition is met.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Design and install a focused Agent Skill from a plain-language request. Use when the user asks to create, add, customize, or install a reusable skill for their Harness agent.
Plan, execute, and verify a trade or position-management request without inventing transaction parameters. Use when the user asks to place, open, buy, sell, long, short, close, cancel, reverse, or otherwise change account state.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
Dispatch one work order to its delegate model via pi, then run the review gate and commit on pass. Use after /factory-prd has written orders and Guillaume confirmed the dispatch plan.
Intake a PRD and decompose it into dispatchable work orders under .factory/orders/. Use when Guillaume supplies a PRD, feature request, or asks to "run this through the factory".
| name | create-routine |
| description | Create or change a recurring market review, alert, or bounded position-management Routine and its optional Mandate. Use when the user asks the agent to remember work on a cadence, monitor a condition, send an alert, or manage a position until a condition is met. |
Use this procedure when the user asks the agent to remember work on a cadence, monitor a condition, send an alert, or manage a position until a condition is met.
A Routine defines when to create a Task and what that Task should accomplish. It never authorizes an Execution.
A Mandate is separate, explicit authority for unattended Execution. Observation and alert Routines do not need a Mandate. Any Routine that may place, change, cancel, or close an order or position does.
Never infer a Mandate from Auto mode, Memory, signer availability, an existing position, or phrases such as “keep an eye on it.”
Confirm or derive only from explicit context:
Use skip for ordinary reviews and alerts. Use coalesce for position
management so concurrent ticks cannot manage the same position in parallel.
Every tick creates a new Task with fresh Observations. Do not reuse a prior quote, portfolio snapshot, Policy Decision, or Receipt.
For unattended Execution, require the user to approve a Mandate that states:
Default to no added exposure. A Routine cannot broaden, renew, or replace its Mandate. PAUSE and signer revocation override it. Budget and execution count must be checked and consumed atomically by the server.
If no valid Mandate exists, a scheduled Task may observe and publish an Artifact. It must not execute or wait indefinitely for interactive approval. Instead, publish that authority or approval is required.
Creating, updating, pausing, or deleting a Routine is a recorded Context Mutation. Granting, changing, revoking, or expiring a Mandate is a distinct Context Mutation. Present both explicitly before persistence.
Examples:
If persistence tools are unavailable, explain what would be created and what information is still missing. Never claim the Routine or Mandate exists.
After persistence, publish an Artifact containing:
