azoth-start

Name: azoth-start
Availability: InStock
Author: yiwei79

Route Codex /start prompts to Azoth command.yaml and body.md workflows.

Updated Apr 8, 2026

Search Tags:#codex #workflow-orchestration #slash-command #prompt-routing #start-workflow #azoth #command-integration

Ready to run

npx skills add https://github.com/yiwei79/azoth --skill azoth-start

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: azoth-start
Source: https://github.com/yiwei79/azoth/tree/main/.agents/skills/azoth-start
Command: npx skills add https://github.com/yiwei79/azoth --skill azoth-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a Codex-visible entrypoint that triggers Azoth's /start workflow from Codex, simplifying user access and routing prompts to the start process.

Core Features & Use Cases

Explicit Codex-native entrypoint for the /start workflow.
Reads execution contract from commands/start/command.yaml and the body from commands/start/body.md.
Preserves the command's stage structure, gate rules, evaluation rules, and the required agent binding.
Accepts user-provided arguments after the trigger and routes them to the start flow.

Quick Start

Invoke the skill in Codex with /start or $azoth-start to begin the Azoth start workflow.

Frequently Asked Questions about azoth-start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trigger the Azoth start workflow from a Codex environment?▼

The Azoth start workflow is triggered in Codex by invoking the /start slash command or the $azoth-start entrypoint, which routes prompts directly to the start process. This provides a native slash command integration for initiating the workflow.

What does prompt routing preserve when executing a slash command workflow?▼

Prompt routing for slash command workflows preserves the stage structure, gate rules, evaluation rules, and required agent binding defined in command.yaml. This ensures workflow orchestration maintains its execution contract and validation gates throughout the process.

Can I pass custom arguments to the start workflow trigger in Codex?▼

Yes, you can pass user-provided arguments after the slash command trigger, and the workflow will route them to the start flow. This allows you to customize execution parameters when initiating the process from Codex.

How does Codex read the execution contract for workflow orchestration?▼

Codex reads the execution contract from commands/start/command.yaml and the workflow body from commands/start/body.md. This file structure defines the stages, gates, and agent bindings required to orchestrate the start process.

Does the start workflow command support the azoth_effect read contract?▼

Yes, the start workflow command supports the azoth_effect: read contract. This ensures the workflow can properly read and interpret the execution contract and body files during the orchestration process.