[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AB0CAZNSSXEAC7F1R1FFP9":3,"skill-same:01M7AB0CAZNSSXEAC7F1R1FFP9":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AB0CAZNSSXEAC7F1R1FFP9","assign-to-workforce",null,"Fan out a converged devague plan's dependency waves to parallel agents in isolated git worktrees, one agent per task per wave, with TDD-gated merges by the main agent. Human gates: the exported spec, the implementation split plan (task map + per-task agent\u002Fmodel proposal + go\u002Fno-go), and the final PR. The devague CLI stays deterministic and non-orchestrating (#20) — it only *describes* the graph via `devague plan waves`; the operator (main agent) performs the fan-out. Use when the user says \"assign to workforce\", \"fan out the plan\", \"parallel subagents\", or after \u002Fspec-to-plan exports a plan. Authored and maintained in agentculture\u002Fdevague (origin = devague); steward pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from steward like the other skills here.","agentculture\u002Fculture-nodes","agentculture","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277824871?v=4","01M7AAZDPCFA8RDCA27DQKKWCJ","AgentCulture","01M7AAZDQ1B6FYE24021YCDAPR",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fassign-to-workforce\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: assign-to-workforce\ntype: command\ndescription: >\n  Fan out a converged devague plan's dependency waves to parallel agents in\n  isolated git worktrees, one agent per task per wave, with TDD-gated merges\n  by the main agent. Human gates: the exported spec, the implementation split\n  plan (task map + per-task agent\u002Fmodel proposal + go\u002Fno-go), and the final PR.\n  The devague CLI stays deterministic and non-orchestrating (#20) — it only\n  *describes* the graph via `devague plan waves`; the operator (main agent)\n  performs the fan-out. Use when the user says \"assign to workforce\",\n  \"fan out the plan\", \"parallel subagents\", or after \u002Fspec-to-plan exports a\n  plan. Authored and maintained in agentculture\u002Fdevague (origin = devague);\n  steward pulls this skill from here and broadcasts it to the AgentCulture\n  mesh — it is NOT vendored from steward like the other skills here.\n---\n\n# assign-to-workforce — fan out a converged plan's waves to parallel agents\n\nThe skill is named **`assign-to-workforce`**; the product\u002FCLI it reads is the\n**`devague plan waves`** command. (The prior leg — turning a spec into a plan —\nis the sibling **`\u002Fspec-to-plan`** skill.)\n\n`assign-to-workforce` takes a **converged devague plan** and fans out its\ndependency waves to parallel agents (subagents, teammate agents, or generalist\nagents) — one agent per task per wave — each working in an **isolated git\nworktree**. The main agent merges each completed worktree gated by TDD. The\nhuman owns exactly three gates: the exported spec, the implementation split\nplan, and the final PR.\n\nThe devague CLI is **never orchestrated by devague itself** — `devague plan\nwaves` describes the dependency graph (#20); it does not spawn agents, manage\nworktrees, mark tasks done, or pick a backend. The fan-out is the *operator's*\njob — this skill and the main agent perform it.\n\n## How to run\n\nThe entry point is `scripts\u002Fassign-to-workforce.sh`. Invoke it from the\nrepository whose plan you are implementing (plans persist under `.devague\u002F`\nin the current directory):\n\n```bash\nbash .claude\u002Fskills\u002Fassign-to-workforce\u002Fscripts\u002Fassign-to-workforce.sh split-plan [--plan \u003Cslug>]\nbash .claude\u002Fskills\u002Fassign-to-workforce\u002Fscripts\u002Fassign-to-workforce.sh waves    [--plan \u003Cslug>] [--json]\nbash .claude\u002Fskills\u002Fassign-to-workforce\u002Fscripts\u002Fassign-to-workforce.sh help\n```\n\nIt resolves the CLI portably — an installed `devague` on `PATH` (the normal\ncase), falling back to `uv run devague` when you are inside the devague\ncheckout, else an install hint. The `split-plan` subcommand reads\n`devague plan waves --json` and renders the human-facing implementation split\nplan: task map, proposed per-task agent + model assignment, and the go\u002Fno-go\nquestion. The `waves` subcommand forwards to `devague plan waves` verbatim.\n\n### Usage\n\n| Subcommand | What it does |\n|------------|--------------|\n| `split-plan [--plan S]` | Read `devague plan waves` and print the implementation split plan — task map with per-task agent + model proposal — ready for human go\u002Fno-go review. |\n| `waves [--plan S] [--json]` | Forward to `devague plan waves [--json]`. Read-only; lists wave batches. On a converged plan exits 0 listing the waves. |\n| `help` | Print usage. |\n\n## The full flow\n\nThe flow has three human gates and one automated TDD merge loop.\n\n### Human gate 1 — the exported spec\n\nThe plan is seeded from a converged frame (`devague plan new --frame \u003Cslug>`).\nThe human reviewed and approved the spec when it was exported by the `\u002Fthink`\nskill. No re-approval needed here — the spec gate is already closed.\n\n### Human gate 2 — the implementation split plan\n\nBefore any task is assigned, the main agent presents the **implementation split\nplan** for human go\u002Fno-go. This is the only gate the human owns at the\nimplementation stage (per task, the TDD gate is the main agent's).\n\nThe split plan contains:\n\n1. **Task map** — every task id, its one-line summary, acceptance criteria, and\n   the wave it belongs to (from `devague plan waves`).\n2. **Per-task agent + model proposal** — for each task: the proposed agent type\n   (subagent \u002F teammate \u002F generalist), the proposed model (e.g. a cheaper\u002Ffaster\n   model for a well-scoped task), and the scope justification (why this task is\n   safe to delegate).\n3. **Go\u002Fno-go question** — explicit human decision: \"Approve this split and\n   assign the plan to the workforce, or edit it first?\"\n\nThe human may edit any row (agent type, model, scope) before approving. The\nplan is model-agnostic — devague does not pick a backend (#20).\n\nRun `split-plan` to print the proposed table:\n\n```bash\nbash .claude\u002Fskills\u002Fassign-to-workforce\u002Fscripts\u002Fassign-to-workforce.sh split-plan\n```\n\nDo not proceed to fan-out until the human approves the split plan.\n\n### Fan-out — one agent per task per wave in isolated worktrees\n\nOnce the human approves, the main agent fans out each wave in order:\n\n1. **Create an isolated git worktree** for each task in the current wave:\n\n   ```bash\n   git worktree add ..\u002Fworktrees\u002Fagent-\u003Ctask-id> -b agent\u002F\u003Ctask-id>\n   ```\n\n2. **Spawn a task agent** inside that worktree (using the approved model from\n   the split plan), with:\n   - The task id, summary, and acceptance criteria as its brief.\n   - Instruction to work **test-first** (TDD): write the failing test(s) that\n     match the acceptance criteria before implementing.\n   - Instruction to commit its work to the worktree branch.\n\n3. **Same-wave tasks run in parallel** (within-wave tasks have no\n   inter-task dependency; the dependency graph guarantees this). Same-file\n   overlap surfaces as a merge conflict at reconcile time, not a live race —\n   isolated worktrees prevent clobbering.\n\n4. **Wait for all tasks in the wave to complete** before starting the next wave.\n\n### TDD-gated merge — main agent, no human per task\n\nFor each completed task worktree, the main agent:\n\n1. **Runs the task's tests before merge** (on the main branch): baseline must\n   pass (or the relevant tests must be absent — the task adds them).\n2. **Merges the worktree branch** into the main branch:\n\n   ```bash\n   git merge --no-ff agent\u002F\u003Ctask-id>\n   ```\n\n3. **Runs the task's tests after merge**: they must pass. If they do not, the\n   merge is reverted and the task agent is given the failure output to fix.\n4. **Removes the worktree** once the merge is accepted:\n\n   ```bash\n   git worktree remove ..\u002Fworktrees\u002Fagent-\u003Ctask-id>\n   ```\n\nThe human does **not** review individual task merges. Per-task acceptance is\nthe main agent's responsibility — the TDD gate (tests pass before AND after\nmerge) plus the task's acceptance criteria. This mirrors the non-authoritative\nworking state pattern of the Human Review Loop (#17): per-task merge records\nare uncommitted working state; the authoritative human gate is the final PR.\n\nAdvance to the next wave only after all tasks in the current wave are merged\nand their tests pass.\n\n### Human gate 3 — the final PR\n\nOnce all waves are merged and the full test suite passes, the main agent opens\na PR via the `cicd` skill (`devex pr open`). The human reviews and merges. This\nis the last and only remaining human gate.\n\n## Hard rules (do not violate)\n\nThese protect the human-gate contract and the TDD guarantee.\n\n- **Present the split plan before any fan-out.** Never spawn a task agent\n  without prior human approval of the implementation split plan (gate 2). The\n  split plan is the human's only implementation-stage decision.\n- **One worktree per task.** Never run two tasks in the same worktree — file\n  contention is managed by isolation, not by trust in the dependency graph.\n  The dependency graph guarantees *logical* independence within a wave, not\n  *file* disjointness. Conflicts surface at merge time.\n- **Tests before AND after merge — no exceptions.** The TDD gate must pass on\n  both sides. A merge that makes tests pass only after (not before) means the\n  baseline was already broken — fix the baseline first.\n- **Human does not gate per-task merges.** The TDD contract replaces the\n  human here. Do not pause for human approval between wave tasks.\n- **devague CLI is not orchestrated.** `devague plan waves` is read-only\n  scheduling metadata (#20). Never run `devague plan` commands inside a task\n  worktree to \"mark a task done\" or modify plan state from a subagent.\n- **Three gates only.** The human's gates are: (1) the exported spec, (2) the\n  implementation split plan, (3) the final PR. No silent fourth gate.\n- **No LLM calls in the devague CLI.** The CLI is deterministic. This skill\n  adds orchestration convention, not CLI behavior.\n\n## Output contract\n\nThe `split-plan` subcommand prints to **stdout** and exits 0 when a converged\nplan is found. On error (no plan, cyclic graph) it exits non-zero with a\n`hint:` line on stderr. The `waves` subcommand forwards the CLI's own output\ncontract (stdout, `--json` for structured output, exit 0 on success).\n\n## Worked example\n\nPicking up after `\u002Fspec-to-plan` exported a plan for the frame `my-feature`:\n\n```bash\na() { bash .claude\u002Fskills\u002Fassign-to-workforce\u002Fscripts\u002Fassign-to-workforce.sh \"$@\"; }\n\n# 1. Inspect the waves\na waves\n\n# 2. Present the implementation split plan for human review\na split-plan\n\n# --- HUMAN: review the table, edit agent\u002Fmodel assignments if needed,\n#     then say \"approved\" to proceed ---\n\n# 3. Fan out wave 1 (t1, t2, t3 are independent — run in parallel)\ngit worktree add ..\u002Fworktrees\u002Fagent-t1 -b agent\u002Ft1\ngit worktree add ..\u002Fworktrees\u002Fagent-t2 -b agent\u002Ft2\ngit worktree add ..\u002Fworktrees\u002Fagent-t3 -b agent\u002Ft3\n# ... spawn task agents in each worktree, await completion ...\n\n# 4. TDD-gated merge for each wave-1 task (no human per task)\ngit merge --no-ff agent\u002Ft1   # tests pass before + after\ngit worktree remove ..\u002Fworktrees\u002Fagent-t1\ngit merge --no-ff agent\u002Ft2\ngit worktree remove ..\u002Fworktrees\u002Fagent-t2\ngit merge --no-ff agent\u002Ft3\ngit worktree remove ..\u002Fworktrees\u002Fagent-t3\n\n# 5. Advance to wave 2 (t4 depends on t1–t3 being merged)\ngit worktree add ..\u002Fworktrees\u002Fagent-t4 -b agent\u002Ft4\n# ... spawn, await, merge with TDD gate, remove worktree ...\n\n# 6. Open the final PR (human gate 3)\nbash .claude\u002Fskills\u002Fcicd\u002Fscripts\u002Fworkflow.sh open\n```\n\nThe exported plan-md from `devague plan export` is the standing brief for\neach task agent — its task id, summary, acceptance criteria, and the targets\nit covers are already in that file.\n\n## Provenance\n\nThis is a **first-party** skill — its origin is `agentculture\u002Fdevague`, where\nthe devague agent maintains it alongside the tools it operates (dogfooding),\nnext to its siblings `\u002Fthink` and `\u002Fspec-to-plan`. It is the *third* skill in\nthat outbound family, covering the implementation leg after a plan converges.\nThe flow runs the *opposite* direction of the vendored steward skills: steward\npulls this **from** devague and broadcasts it to the rest of the AgentCulture\nmesh. The `cite, don't import` policy still holds: downstream repos copy it,\nthey don't symlink or depend on it. See `docs\u002Fskill-sources.md`.\n","# assign-to-workforce — fan out a converged plan's waves to parallel agents\n\nThe skill is named **`assign-to-workforce`**; the product\u002FCLI it reads is the\n**`devague plan waves`** command. (The prior leg — turning a spec into a plan —\nis the sibling **`\u002Fspec-to-plan`** skill.)\n\n`assign-to-workforce` takes a **converged devague plan** and fans out its\ndependency waves to parallel agents (subagents, teammate agents, or generalist\nagents) — one agent per task per wave — each working in an **isolated git\nworktree**. The main agent merges each completed worktree gated by TDD. The\nhuman owns exactly three gates: the exported spec, the implementation split\nplan, and the final PR.\n\nThe devague CLI is **never orchestrated by devague itself** — `devague plan\nwaves` describes the dependency graph (#20); it does not spawn agents, manage\nworktrees, mark tasks done, or pick a backend. The fan-out is the *operator's*\njob — this skill and the main agent perform it.\n\n## How to run\n\nThe entry point is `scripts\u002Fassign-to-workforce.sh`. Invoke it from the\nrepository whose plan you are implementing (plans persist under `.devague\u002F`\nin the current directory):\n\n```bash\nbash .claude\u002Fskills\u002Fassign-to-workforce\u002Fscripts\u002Fassign-to-workforce.sh split-plan [--plan \u003Cslug>]\nbash .claude\u002Fskills\u002Fassign-to-workforce\u002Fscripts\u002Fassign-to-workforce.sh waves    [--plan \u003Cslug>] [--json]\nbash .claude\u002Fskills\u002Fassign-to-workforce\u002Fscripts\u002Fassign-to-workforce.sh help\n```\n\nIt resolves the CLI portably — an installed `devague` on `PATH` (the normal\ncase), falling back to `uv run devague` when you are inside the devague\ncheckout, else an install hint. The `split-plan` subcommand reads\n`devague plan waves --json` and renders the human-facing implementation split\nplan: task map, proposed per-task agent + model assignment, and the go\u002Fno-go\nquestion. The `waves` subcommand forwards to `devague plan waves` verbatim.\n\n### Usage\n\n| Subcommand | What it does |\n|------------|--------------|\n| `split-plan [--plan S]` | Read `devague plan waves` and print the implementation split plan — task map with per-task agent + model proposal — ready for human go\u002Fno-go review. |\n| `waves [--plan S] [--json]` | Forward to `devague plan waves [--json]`. Read-only; lists wave batches. On a converged plan exits 0 listing the waves. |\n| `help` | Print usage. |\n\n## The full flow\n\nThe flow has three human gates and one automated TDD merge loop.\n\n### Human gate 1 — the exported spec\n\nThe plan is seeded from a converged frame (`devague plan new --frame \u003Cslug>`).\nThe human reviewed and approved the spec when it was exported by the `\u002Fthink`\nskill. No re-approval needed here — the spec gate is already closed.\n\n### Human gate 2 — the implementation split plan\n\nBefore any task is assigned, the main agent presents the **implementation split\nplan** for human go\u002Fno-go. This is the only gate the human owns at the\nimplementation stage (per task, the TDD gate is the main agent's).\n\nThe split plan contains:\n\n1. **Task map** — every task id, its one-line summary, acceptance criteria, and\n   the wave it belongs to (from `devague plan waves`).\n2. **Per-task agent + model proposal** — for each task: the proposed agent type\n   (subagent \u002F teammate \u002F generalist), the proposed model (e.g. a cheaper\u002Ffaster\n   model for a well-scoped task), and the scope justification (why this task is\n   safe to delegate).\n3. **Go\u002Fno-go question** — explicit human decision: \"Approve this split and\n   assign the plan to the workforce, or edit it first?\"\n\nThe human may edit any row (agent type, model, scope) before approving. The\nplan is model-agnostic — devague does not pick a backend (#20).\n\nRun `split-plan` to print the proposed table:\n\n```bash\nbash .claude\u002Fskills\u002Fassign-to-workforce\u002Fscripts\u002Fassign-to-workforce.sh split-plan\n```\n\nDo not proceed to fan-out until the human approves the split plan.\n\n### Fan-out — one agent per task per wave in isolated worktrees\n\nOnce the human approves, the main agent fans out each wave in order:\n\n1. **Create an isolated git worktree** for each task in the current wave:\n\n   ```bash\n   git worktree add ..\u002Fworktrees\u002Fagent-\u003Ctask-id> -b agent\u002F\u003Ctask-id>\n   ```\n\n2. **Spawn a task agent** inside that worktree (using the approved model from\n   the split plan), with:\n   - The task id, summary, and acceptance criteria as its brief.\n   - Instruction to work **test-first** (TDD): write the failing test(s) that\n     match the acceptance criteria before implementing.\n   - Instruction to commit its work to the worktree branch.\n\n3. **Same-wave tasks run in parallel** (within-wave tasks have no\n   inter-task dependency; the dependency graph guarantees this). Same-file\n   overlap surfaces as a merge conflict at reconcile time, not a live race —\n   isolated worktrees prevent clobbering.\n\n4. **Wait for all tasks in the wave to complete** before starting the next wave.\n\n### TDD-gated merge — main agent, no human per task\n\nFor each completed task worktree, the main agent:\n\n1. **Runs the task's tests before merge** (on the main branch): baseline must\n   pass (or the relevant tests must be absent — the task adds them).\n2. **Merges the worktree branch** into the main branch:\n\n   ```bash\n   git merge --no-ff agent\u002F\u003Ctask-id>\n   ```\n\n3. **Runs the task's tests after merge**: they must pass. If they do not, the\n   merge is reverted and the task agent is given the failure output to fix.\n4. **Removes the worktree** once the merge is accepted:\n\n   ```bash\n   git worktree remove ..\u002Fworktrees\u002Fagent-\u003Ctask-id>\n   ```\n\nThe human does **not** review individual task merges. Per-task acceptance is\nthe main agent's responsibility — the TDD gate (tests pass before AND after\nmerge) plus the task's acceptance criteria. This mirrors the non-authoritative\nworking state pattern of the Human Review Loop (#17): per-task merge records\nare uncommitted working state; the authoritative human gate is the final PR.\n\nAdvance to the next wave only after all tasks in the current wave are merged\nand their tests pass.\n\n### Human gate 3 — the final PR\n\nOnce all waves are merged and the full test suite passes, the main agent opens\na PR via the `cicd` skill (`devex pr open`). The human reviews and merges. This\nis the last and only remaining human gate.\n\n## Hard rules (do not violate)\n\nThese protect the human-gate contract and the TDD guarantee.\n\n- **Present the split plan before any fan-out.** Never spawn a task agent\n  without prior human approval of the implementation split plan (gate 2). The\n  split plan is the human's only implementation-stage decision.\n- **One worktree per task.** Never run two tasks in the same worktree — file\n  contention is managed by isolation, not by trust in the dependency graph.\n  The dependency graph guarantees *logical* independence within a wave, not\n  *file* disjointness. Conflicts surface at merge time.\n- **Tests before AND after merge — no exceptions.** The TDD gate must pass on\n  both sides. A merge that makes tests pass only after (not before) means the\n  baseline was already broken — fix the baseline first.\n- **Human does not gate per-task merges.** The TDD contract replaces the\n  human here. Do not pause for human approval between wave tasks.\n- **devague CLI is not orchestrated.** `devague plan waves` is read-only\n  scheduling metadata (#20). Never run `devague plan` commands inside a task\n  worktree to \"mark a task done\" or modify plan state from a subagent.\n- **Three gates only.** The human's gates are: (1) the exported spec, (2) the\n  implementation split plan, (3) the final PR. No silent fourth gate.\n- **No LLM calls in the devague CLI.** The CLI is deterministic. This skill\n  adds orchestration convention, not CLI behavior.\n\n## Output contract\n\nThe `split-plan` subcommand prints to **stdout** and exits 0 when a converged\nplan is found. On error (no plan, cyclic graph) it exits non-zero with a\n`hint:` line on stderr. The `waves` subcommand forwards the CLI's own output\ncontract (stdout, `--json` for structured output, exit 0 on success).\n\n## Worked example\n\nPicking up after `\u002Fspec-to-plan` exported a plan for the frame `my-feature`:\n\n```bash\na() { bash .claude\u002Fskills\u002Fassign-to-workforce\u002Fscripts\u002Fassign-to-workforce.sh \"$@\"; }\n\n# 1. Inspect the waves\na waves\n\n# 2. Present the implementation split plan for human review\na split-plan\n\n# --- HUMAN: review the table, edit agent\u002Fmodel assignments if needed,\n#     then say \"approved\" to proceed ---\n\n# 3. Fan out wave 1 (t1, t2, t3 are independent — run in parallel)\ngit worktree add ..\u002Fworktrees\u002Fagent-t1 -b agent\u002Ft1\ngit worktree add ..\u002Fworktrees\u002Fagent-t2 -b agent\u002Ft2\ngit worktree add ..\u002Fworktrees\u002Fagent-t3 -b agent\u002Ft3\n# ... spawn task agents in each worktree, await completion ...\n\n# 4. TDD-gated merge for each wave-1 task (no human per task)\ngit merge --no-ff agent\u002Ft1   # tests pass before + after\ngit worktree remove ..\u002Fworktrees\u002Fagent-t1\ngit merge --no-ff agent\u002Ft2\ngit worktree remove ..\u002Fworktrees\u002Fagent-t2\ngit merge --no-ff agent\u002Ft3\ngit worktree remove ..\u002Fworktrees\u002Fagent-t3\n\n# 5. Advance to wave 2 (t4 depends on t1–t3 being merged)\ngit worktree add ..\u002Fworktrees\u002Fagent-t4 -b agent\u002Ft4\n# ... spawn, await, merge with TDD gate, remove worktree ...\n\n# 6. Open the final PR (human gate 3)\nbash .claude\u002Fskills\u002Fcicd\u002Fscripts\u002Fworkflow.sh open\n```\n\nThe exported plan-md from `devague plan export` is the standing brief for\neach task agent — its task id, summary, acceptance criteria, and the targets\nit covers are already in that file.\n\n## Provenance\n\nThis is a **first-party** skill — its origin is `agentculture\u002Fdevague`, where\nthe devague agent maintains it alongside the tools it operates (dogfooding),\nnext to its siblings `\u002Fthink` and `\u002Fspec-to-plan`. It is the *third* skill in\nthat outbound family, covering the implementation leg after a plan converges.\nThe flow runs the *opposite* direction of the vendored steward skills: steward\npulls this **from** devague and broadcasts it to the rest of the AgentCulture\nmesh. The `cite, don't import` policy still holds: downstream repos copy it,\nthey don't symlink or depend on it. See `docs\u002Fskill-sources.md`.\n",{"name":5,"type":24,"description":7},"command","main","a2056e6191a4e106faf886773efed2f44ff120b2",".claude\u002Fskills\u002Fassign-to-workforce",0,"https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes","https:\u002F\u002Fgithub.com\u002Fagentculture","https:\u002F\u002Fagentculture.org","Agent first OSS software","2026-09-29 08:50:58",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add agentculture\u002Fculture-nodes --skill assign-to-workforce",{"tool":40,"command":41},"bunx","bunx skills add agentculture\u002Fculture-nodes --skill assign-to-workforce",{"tool":43,"command":44},"pnpm","pnpm dlx skills add agentculture\u002Fculture-nodes --skill assign-to-workforce","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fassign-to-workforce\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Fassign-to-workforce.sh","SCRIPT","脚本",7631,"https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fassign-to-workforce\u002Fscripts\u002Fassign-to-workforce.sh",[55,62,67,72,79,86],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7AB6FGWR0P3SPYFX2W801D5","sample","Fixture skill proving the .qwen\u002Fskills leg carries at least one skill.","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002Fadapters\u002Fqwen\u002Ftests\u002Ffixtures\u002Fconfig-repo-no-culture-yaml\u002F.qwen\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":63,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AB6E9PFCDZE193CGPM0K35","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002Fadapters\u002Fqwen\u002Ftests\u002Ffixtures\u002Fconfig-repo-no-agents-md\u002F.qwen\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":68,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7AB6CJ3G1ZZJD63NEZZK1JH","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002Fadapters\u002Fqwen\u002Ftests\u002Ffixtures\u002Fconfig-repo-complete\u002F.qwen\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AB64WWKV9H2J7JDV5KXGPA","think","Think a vague feature idea into a buildable spec by working backwards (the idea→spec leg; drives the `devague` CLI). Start from the announcement (\"pretend it shipped\"), capture and classify claims, interrogate them with honesty conditions and hard questions, park open vagueness as a first-class object, and export a spec only once the frame *converges*. Use when the user says \"think this through\", \"spec this\", \"work backwards\", \"turn this idea into a spec\", \"announcement frame\", or \"devague\", or when a feature request is too vague to build yet. Explore scope first when the idea touches an existing codebase — the sibling `scope` skill is the optional opening leg ahead of `think`. Once a spec exports, hand off to the sibling `spec-to-plan` skill to turn it into a plan. Authored and maintained in agentculture\u002Fdevague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the other skills here.","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fthink\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AB5X0FTZ081AFH3BTGQKVA","summarize-delivery","Close the loop after an `assign-to-workforce` run by turning what actually happened into an accountability artifact — planned versus actual delivery, mid-work decisions, plan drift, evidence-backed delivery claims, and remaining work. The plan the user confirmed is the contract; this skill records where execution obeyed it, where it changed, and what is genuinely safe to claim as delivered. Runs on complete, partial, AND failed runs — failure is reported faithfully, never smoothed over. Use when the user says \"summarize delivery\", \"delivery summary\", \"wrap up\", \"close the loop\", \"what did we actually ship\", or \"plan versus actual\", or after `assign-to-workforce` merges (or fails to merge) a plan's waves. Authored and maintained in agentculture\u002Fdevague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the inbound skills here.","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fsummarize-delivery\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7AB5NA0QY9NN076N24NJPJQ","spec-to-plan","Turn a converged devague spec into a buildable plan by working forwards (the spec→plan leg; drives the `devague plan` CLI group). Seed a plan from a converged frame, add tasks that collectively cover every coverage target (the frame's confirmed claims + honesty conditions), give each task acceptance criteria and an honest dependency order, park genuine unknowns as first-class risks, and export a plan only once it *converges*. Use when the user says \"spec to plan\", \"stp\", \"turn this spec into a plan\", \"plan this spec\", \"make a build plan\", or after the `think` skill exports a spec. Authored and maintained in agentculture\u002Fdevague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the other skills here.","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fspec-to-plan\u002FSKILL.md",[],[]]