Change the workspace deliberately

Use these skills to make managed local changes or establish optional suitability context. A clear intent marker keeps workspace edits distinct from ordinary analysis and from final broker actions.

Know what an update owns #

TradingCodex replaces exact product files recorded in .tradingcodex/generated/module-lock.json, including generated Codex configuration, hooks, bundled tcx-* skills, schemas, policies, and launchers. Do not customize those files directly.

Keep durable customization in the managed surfaces: additional agent instructions, strategy-* skills, optional role skills, Investment Brain sources and lifecycle state, and workspace customization or Investor Context. Research, reports, forecasts, decisions, and run records are workspace artifacts and survive an update. Parent folders such as .agents/skills/, .tradingcodex/, and trading/ contain more than one ownership class, so the exact file or reserved prefix matters.

.gitignore is the special mixed file: TradingCodex updates only its marked privacy block and keeps user rules outside it. Generated .codex/config.toml remains product-managed, but update preserves non-reserved user MCP, plugin, and skill entries while rebuilding only TradingCodex-owned projections. User capability lifecycle remains native Codex functionality.

Read each skill #

01tcx-buildOpen a managed workspace Build turn.→02tcx-investor-contextPreview and apply optional suitability context.→

Primary

`tcx-build`

Mark one exact root turn as explicit workspace-local Build intent.

Use it when: You need a workspace refresh, optional role skill, or connector/provider development. Brain, community Wiki, and Strategy lifecycle management use their own scoped tasks.
Order onboarding: For a provider connection through ticket, approval, and final action, follow From provider to order.
Exact posture: Select trading-build and start a new native task. Put $tcx-build on the first meaningful line as a plain token or matching workspace skill link; the concrete request may share the line or follow it.
What the marker does: It creates a workspace/session/turn/prompt-bound intent grant for protected managed work during that root turn.
What it does not do: It does not elevate the actual profile, manage user-installed Codex capabilities, touch raw credentials, publish Git changes, authorize an order, or manage a Brain, Wiki, or Strategy.

Managed workspace update

$tcx-build
Update this workspace to the current compatible package and show the resulting status.

Plan mode cannot issue or use this grant. Subagents cannot create or inherit it, and every mutating follow-up or scheduled task needs a fresh exact marker.

Supporting

`tcx-investor-context`

Interview and preview optional workspace-local suitability context.

Use it when: You want to discuss objective, horizon, loss capacity, liquidity needs, concentrations, or tax and account constraints.
What it returns: User-confirmed proposed values, a preview of gaps and default application state, plus one exact user-terminal command for any persistent update.
At runtime: The workspace’s saved application default determines whether it is sealed into a run; the read-only viewer offers no one-run override.
Boundary: It does not store secrets, grant authority, run investment analysis, or change broker and policy gates.

Define optional suitability context

$tcx-investor-context
Help me define the optional suitability context for this workspace.

Read the context model →Read the workspace contract →