菜单
System design phase — architecture, tech-stack options, module boundaries, data model, and ADRs from a validated SRS. Use after requirements are validated, when choosing a tech stack, designing system structure/APIs/data models, or recording an architecture decision.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AnmarHani/SwarmVault --skill swarm-design命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Implementation phase — turn a validated design into dependency-ordered tickets, then work them as one of N parallel agents with atomic claims, model tiering, and tests-in-ticket definition of done. Use to plan tickets from a design, pick up/continue implementation work, coordinate parallel agents, or check what to build next.
Optional autonomy control plane — configure, plan, launch, monitor, recover, or stop local CLI-agent workers through SwarmVault's durable supervisor. Use for fit/budget-aware platform + model + reasoning-effort routing; a consistent pre-start/live/boundary/on-demand board with ticket drill-down; TOLD/MEASURED/EST usage and run accounting; bounded event-driven waits; stale-worker and possible-quota recovery; safe context compaction; launch adapters; and consent-gated continuation across provider resets.
Start a new project connected to the SwarmVault — register it, wire platform adapters, offer git init, set vault-as-default. Use when starting a new project, connecting a project to the vault, or when the user asks to set up SwarmVault in a directory.
基于 SOC 职业分类
正在显示 SKILL.md
| name | swarm-design |
| description | System design phase — architecture, tech-stack options, module boundaries, data model, and ADRs from a validated SRS. Use after requirements are validated, when choosing a tech stack, designing system structure/APIs/data models, or recording an architecture decision. |
Gate: requires a validated SRS (else route back to swarm-spec). Read the SRS and feature specs first; the design must answer them, not your habits.
Lane: this is the standard, agent-driven lane — you propose, the user validates. If the user wants to own the system rather than receive it (deep design, pseudocode, algorithm-level planning, "developer mode"), hand the phase to swarm-design-deep instead; the two replace each other and never run together.
50 Decisions/<P>/ADR-NNN-<slug>.md (template:
90 Templates/decision.md): context, options, decision, consequences, FR/NFR links.docs/design.md (human lane) + ADRs, mirrored to the vault by sync. End with the user
validation gate (gated mode) or a self-check against the traceability table (auto mode);
update flow-state to phase: design-ui (if the SRS declares an interface) or
phase: tickets.
Influences: Jeffallan's architecture-designer & api-designer; Pocock's codebase-design & domain-modeling; refactoring.guru; Nygard ADRs — see CREDITS.md.