# Workflow 6ayh

> 6AO workflow detail layer for progressive optimization and refactor work after workflow selection is known. Use when the task is already confirmed as 6AO, the user explicitly requests @6AO or legacy alias @6AYH, or intake has classified the task as gradual optimization, refactoring, maintenance-cost reduction, or performance cleanup. Produces dated and versioned workflow docs under the active project's root docs/YYYY_MM_DD_中文任务名_vN/ directory.

- Skill: `awfaups/workflow-6ayh` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add awfaups/workflow-6ayh`
- Raw SKILL.md: https://api.skillmd.com/api/skills/awfaups/workflow-6ayh/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: awfaups (https://skillmd.com/u/awfaups)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/awfaups/workflow-6ayh

---


# Workflow 6AO

Use this skill only when the workflow type is already known to be `6AO`.

Treat this skill as a detail layer, not a public governance entry.

- If the request still needs intake, routing, or cross-role governance, enter through `@intake` first.
- Use this skill after workflow selection is settled.
- Keep global handoff policy in `intake-governance`; keep 6AO stage rules here and in `references/6ayh.md`.

## Activation response

> ✅ 6A Optimization 工作流（6AO）已激活
> 当前阶段：Align（目标与风险对齐）

## Execution contract

This skill enforces:

- progressive optimization only
- required docs as mandatory deliverables
- docs under `docs/YYYY_MM_DD_中文任务名_vN/`
- Align, Architect, Atomize, Approve, Automate, and Assess gates
- current-state and risk analysis before design
- explicit behavior-preservation and rollback expectations
- user clarification for contract changes, risky changes, or preference-heavy decisions
- explicit user confirmation of the document bundle before code generation
- characterization tests before refactoring when existing behavior is underspecified
- code-change records with file path, line range, before context, and after context
- no execution before workflow docs exist and the user has confirmed them

## Read next

- `references/6ayh.md`