azoth-context-architect

Define the Codex-visible entrypoint for Azoth's /context-architect workflow.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill azoth-context-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azoth-context-architect
Source: https://github.com/yiwei79/azoth/tree/main/.agents/skills/azoth-context-architect
Command: npx skills add https://github.com/yiwei79/azoth --skill azoth-context-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a Codex-visible entrypoint for Azoth's /context-architect workflow, consolidating access and ensuring a consistent execution contract across tools and prompts.

Core Features & Use Cases

  • Codex-native surface: exposes the /context-architect workflow as a first-class Codex command surface.
  • Execution contract discipline: reads the canonical instructions from .claude/commands/context-architect.md and enforces argument handling, stage rules, gate logic, and the orchestrator binding.
  • Safe, auditable execution: preserves references to skills/agents and applies guardrails to maintain predictable results.

Quick Start

Invoke the /azoth-context-architect command in Codex to start the /context-architect workflow with your prompt.

Frequently Asked Questions about azoth-context-architect

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

FAQPage Schema
How do I expose a custom workflow as a Codex command surface?

This Skill exposes a custom workflow as a Codex command surface by extracting arguments after the /azoth-context-architect trigger and preserving command stages, gates, and evaluation rules for consistent execution.

How do I enforce an execution contract for a command workflow across Codex CLI and UI?

You can enforce an execution contract for a command workflow across Codex CLI and UI by reading the canonical instructions from .claude/commands/context-architect.md, which ensures argument handling and gate logic are strictly applied.

Can I use Codex commands to trigger an orchestrator binding with safe execution?

Yes, you can trigger an orchestrator binding with safe execution in Codex by applying the azoth_effect: read guardrail, which ensures constrained, predictable execution while preserving references to skills and agents.

What is the best way to consolidate access to an Azoth workflow in Codex?

The best way to consolidate access to an Azoth workflow in Codex is to define a first-class command entrypoint that extracts trigger arguments and honors authoritative workflow rules for safe, auditable execution.

How do I start the context-architect workflow from a prompt in Codex?

To start the context-architect workflow from a prompt in Codex, invoke the /azoth-context-architect command with your prompt, and the Skill will extract the arguments to initiate the workflow.