myco:author-harness-task

You define a phased task by creating a TypeScript file exporting a typed TaskDefinition with configured phases and triggers in the designated tasks directory. This registers the structured task lifecycle for the Myco agent harness.

Phase workflow design lets you configure specific 'discover' and 'write' phases with individual budgets, tool surfaces, and model selection. This ensures each phase of the TaskDefinition executes within its calibrated resource limits.

Yes, a running daemon is required to load and test a new TaskDefinition. After placing the TypeScript task file in the correct directory, restarting the daemon registers the configuration so you can validate the phased execution.

The best way to configure session gating and triggers is within the TaskDefinition scaffold. This structured method maps phase workflows to specific triggers and gates reliable task lifecycles from discovery to execution.

Phased executor tasks failing during diagnostics can be inspected by checking agent_runs. The TaskDefinition framework provides observability into these runs to help debug phase workflows, budgets, and tool surfaces.