azoth-arch-proposal

Trigger Codex-driven architecture proposals for Azoth's `/arch-proposal` workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill serves as the Codex-visible entrypoint for Azoth's architecture proposal workflow, enabling users to trigger the /arch-proposal process from Codex with a stable, discoverable command surface.

Core Features & Use Cases

  • Codex-native entrypoint to initiate the architecture proposal workflow from Codex.
  • Command surface parity with the /arch-proposal UX, preserving stages, gates, and evaluation rules.
  • Execution contract and guidance by reading the canonical .claude/commands/arch-proposal.md and applying it to user prompts.

Quick Start

Invoke this skill with a prompt to start the architecture proposal workflow and capture the results.

Frequently Asked Questions about azoth-arch-proposal

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

FAQPage Schema
How do I trigger an architecture proposal workflow from Codex?

Trigger the architecture proposal workflow from Codex by invoking this dedicated entrypoint with a prompt. It initiates Azoth's `/arch-proposal` process while preserving command structure, gating, and evaluation rules.

What is the `/arch-proposal` command in Azoth used for?

The `/arch-proposal` process is used to create and manage architecture proposals. This entrypoint reads the canonical `.claude/commands/arch-proposal.md` file to apply execution contracts and agent bindings to your prompts.

Can I use slash commands and CLI to manage architecture proposals in Codex?

Yes, slash commands and CLI are both supported for managing architecture proposals in Codex. The entrypoint applies command surface parity across these interfaces to ensure consistent stages and gates.

How do I start an architecture proposal with a prompt in Codex?

Start an architecture proposal by invoking this skill with your prompt to capture results. It serves as the Codex-native entrypoint, applying the `azoth_effect: mixed` contract to the proposal creation.

Do I need specific files to preserve command structure during proposal creation?

You need the canonical `.claude/commands/arch-proposal.md` file to preserve command structure during proposal creation. The workflow requires reading this file to maintain agent bindings and evaluation rules.