Workflow 6ayh

Skill awfaups/intake-governance/skills/workflow-6ayh

Portable multi-agent governance skill for role-based planning, review, dispatch, and execution.

Install

npx -y skills add awfaups/intake-governance --skill workflow-6ayh

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.md

1.8 KB, as published. Nobody here has run it

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

Gives 0 of the 12 instructions most performance cost skills give

Counted across 803 of the 1,058 authors here whose files we hold, read 2026-08-06

keep skill files under 500 linesin 82 of 803, across 17 files
use imperative form in instructionsin 81 of 803, across 10 files
draft assertions while test runs are in progressin 75 of 803, across 9 files
create two to three realistic test promptsin 74 of 803, across 8 files
write skill descriptions to be pushyin 72 of 803, across 7 files
save test cases to evals jsonin 72 of 803, across 6 files
ask questions about edge cases and input formatsin 71 of 803, across 6 files
save timing data immediately when runs completein 70 of 803, across 5 files
include all trigger conditions in the skill descriptionin 69 of 803, across 3 files
launch all test runs in a single turnin 69 of 803, across 3 files
capture intent before writing a skillin 67 of 803, across 1 file
import directly instead of barrel filesin 52 of 803, across 15 files

Said here and by no other author read

activate only when workflow type is 6AO
enter through intake if request needs routing
enforce progressive optimization only
create docs under dated versioned directories
perform current-state and risk analysis before design
request user clarification for risky changes

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.