ワンクリックでManusで任意のスキルを実行

wf-max

スター3

フォーク0

更新日2026年7月4日 10:30

Use for /wf-max in Claude Code, $wf-max or /skills wf-max in Codex, or maximum-parallelism Harness work with WF strict-superset gates and CEO -> manager -> worker decomposition.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

LiWeny16

LiWeny16/LetShare

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

WF-MAX Adapter

The authoritative workflow lives in Harness/WF-MAX.md; this adapter only routes and summarizes hard constraints.

Invocation

Claude Code: /wf-max [task]
Codex: $wf-max or /skills then choose wf-max

Load

CLAUDE.md
Harness/MEMORY.md
Harness/README.md
Harness/WF-MAX.md
Harness/subagents.md
Harness/dispatch.md
Harness/agent-workflow.md

Rules

WF-MAX is a WF strict superset: every WF role, gate, and acceptance rule still applies, then execution expands through:

Global mode: wf-max
Agent role: ceo | manager | worker | reviewer | verifier | reflector
Dispatch permission: writeSet, forbidden, verification

CEO reads, plans, dispatches, synthesizes, and writes task state only. CEO never edits production source.
Workers edit only the dispatch writeSet; outside write set is blocked.
Managers coordinate and synthesize. Reviewers read/report only.
D-GATE is mandatory before implementation waves: dispatch table, AC IDs, disjoint file claims, self-audit, and reviewer plan.
Final acceptance requires verifier evidence, cross-review, and reflector PASS.

Fan-Out Discipline

Use as many useful subagents as the runtime safely allows.
Codex capacity may be configured through official agents.max_threads and agents.max_depth; generated Harness config defaults to .codex/config.toml with max_threads = 12 and max_depth = 1.
Close completed agents before declaring the pool exhausted.
If Codex remains bottlenecked, ask the user before raising agents.max_threads above the scaffold default. Do not silently edit project or global Codex config.
Keep agents.max_depth = 1 unless the user explicitly approves recursive delegation.
If the current runtime is exhausted, overflow to the other CLI with explicit dispatch packets: Codex -> claude -p; Claude -> available Codex CLI such as codex exec.
Do not rely on undocumented config, environment variables, forked/derived conversations, Codex++, local patches, or third-party forks as stable ways to remove subagent limits.
Fall back to bounded role passes only when native subagents and cross-CLI overflow are unavailable; record the fallback in the task PLAN.

このリポジトリの他の Skills

同じリポジトリ

subagent-orchestrator

LiWeny16/LetShare

Use when work needs bounded subagent coordination, parallel read-only exploration, independent review gates, broad context partitioning, or controlled handoffs.

2026-07-043

tdd

LiWeny16/LetShare

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

2026-07-043

wf-auto

LiWeny16/LetShare

Perpetual auto-optimization mode. Never stops until 8-angle exhaustion. Inherits WF acceptance gates and subagent orchestration per cycle. Use for Claude /wf-auto, Codex $wf-auto, auto mode, or unbounded self-directed optimization.

2026-07-043

wf-auto-spark

LiWeny16/LetShare

Perpetual inspiration mode for /wf-auto-spark or $wf-auto-spark. Inherits WF-AUTO/WF execution gates while using external spark search, roadmap anchoring, and <=50% deviation guard.

2026-07-043

wf-learn

LiWeny16/LetShare

Use for /wf-learn in Claude Code, $wf-learn or /skills wf-learn in Codex, or when the user wants a learning cycle from repeated errors, corrections, patterns, or session history.

2026-07-043

wf-readme

LiWeny16/LetShare

Use when a project README already exists and the user asks to preserve, merge, modernize, optimize, or clarify repository documentation during harness install or documentation work.

2026-07-043

WF-MAX Adapter

The authoritative workflow lives in Harness/WF-MAX.md; this adapter only routes and summarizes hard constraints.

Invocation

Claude Code: /wf-max [task]

Codex: $wf-max or /skills then choose wf-max

Load

CLAUDE.md

Harness/MEMORY.md

Harness/README.md

Harness/WF-MAX.md

Harness/subagents.md

Harness/dispatch.md

Harness/agent-workflow.md

Rules

WF-MAX is a WF strict superset: every WF role, gate, and acceptance rule still applies, then execution expands through:

Global mode: wf-max

Dispatch permission: writeSet, forbidden, verification

CEO reads, plans, dispatches, synthesizes, and writes task state only. CEO never edits production source.

Workers edit only the dispatch writeSet; outside write set is blocked.

Managers coordinate and synthesize. Reviewers read/report only.

D-GATE is mandatory before implementation waves: dispatch table, AC IDs, disjoint file claims, self-audit, and reviewer plan.

Final acceptance requires verifier evidence, cross-review, and reflector PASS.

Fan-Out Discipline

Use as many useful subagents as the runtime safely allows.

Codex capacity may be configured through official agents.max_threads and agents.max_depth; generated Harness config defaults to .codex/config.toml with max_threads = 12 and max_depth = 1.

Close completed agents before declaring the pool exhausted.

If Codex remains bottlenecked, ask the user before raising agents.max_threads above the scaffold default. Do not silently edit project or global Codex config.

Keep agents.max_depth = 1 unless the user explicitly approves recursive delegation.

If the current runtime is exhausted, overflow to the other CLI with explicit dispatch packets: Codex -> claude -p; Claude -> available Codex CLI such as codex exec.

Do not rely on undocumented config, environment variables, forked/derived conversations, Codex++, local patches, or third-party forks as stable ways to remove subagent limits.

Fall back to bounded role passes only when native subagents and cross-CLI overflow are unavailable; record the fallback in the task PLAN.

name	wf-max
description	Use for /wf-max in Claude Code, $wf-max or /skills wf-max in Codex, or maximum-parallelism Harness work with WF strict-superset gates and CEO -> manager -> worker decomposition.