WBS Planner

Work Breakdown Structure for multi-agent project management. Organize work as Roadmap → Epic → Task hierarchy with templates and granularity standards. Use w...

Security Scan

This is an instruction-only Work Breakdown Structure (WBS) skill whose files, templates, and runtime instructions are consistent with project-planning and task-template responsibilities; it asks for no credentials or installs and contains no hidden endpoints.

Purpose & Capability

The name/description (WBS Planner) match the provided templates, roadmaps, epic/task templates, and workflow docs. All required actions (creating roadmap/, epic/, and task files; checking task granularity; following PM/Dev workflows) are appropriate for a planning/templating skill and do not require extra credentials or external services.

Instruction Scope

The SKILL.md and referenced docs instruct the agent to read and write project files (roadmap/roadmap.md, epic.md, TASK.md) and to follow PM/Dev workflows — this is expected. Two references mention agent-side actions ('编码（源代码修改使用 codex exec，参考 coding-agent skill）' and using 'sessions_send' to notify a dev), which are references to other agent capabilities rather than hidden network endpoints. These are not inherently malicious, but they imply the agent may be expected to execute code or send notifications if the environment grants those capabilities. If you don't want the agent to have roam-to-edit or notify privileges, restrict its workspace and messaging permissions.

Install Mechanism

No install spec and no code files to execute; the skill is instruction-only so nothing is downloaded or written to disk by an installer.

Credentials

The skill declares no required environment variables, no credentials, and no config paths. The actions described (editing project markdown and following templates) do not justify extra secrets or system access.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request permanent inclusion or claim to modify other skills or global settings. The workflows assume the agent can modify files in the project workspace — normal for a planning skill — so ensure the agent's workspace permissions are appropriate.

Assessment

This skill is instruction-only and coherent with its stated purpose: it provides templates and guidance for creating roadmap/epic/task markdown files and for PM/Dev workflows. Before installing: 1) Confirm you are comfortable letting the agent read/write project files in the workspace (the skill expects to open and create roadmap/epic/task files). 2) Note the docs mention agent capabilities like 'codex exec' and 'sessions_send' — those are NOT included in the skill but indicate it may expect the agent to execute code or send notifications if your agent environment grants those APIs; limit those capabilities if you don't want autonomous code execution or external notifications. 3) Test the skill in a disposable or sample repository first to confirm behavior. If the skill later requests environment variables, external URLs, or an installer, reassess — that would raise concern.

将项目工作从宏观到微观逐层分解：Roadmap → Epic → Task。

三层结构

层级	定义	负责人
Roadmap	产品路线图，规划所有 Epic 的优先级和时间线	创始人 / PM
Epic	大功能模块，包含多个 Task	PM 规划
Task	可分配给单人、1-2 个工作周期内完成的具体任务	PM 创建，Dev 执行

项目目录结构

在项目根目录下创建 roadmap/ 目录：

roadmap/
├── roadmap.md
├── epic-001-feature-name/
│   ├── epic.md
│   ├── task-001-name.md
│   ├── task-002-name.md
│   └── task-003-name.md
├── epic-002-feature-name/
│   ├── epic.md
│   └── task-001-name.md
└── ...

命名规则：

• Epic 目录：epic-NNN-简短英文名
• Task 文件：task-NNN-简短英文名.md
• 编号在各自层级内递增

模板文件见 templates/ 目录。

Task 粒度标准

这是整个体系的核心。Task 拆得不够细，验收就容易失败。

一个合格的 Task 必须同时满足：

1. 单一交付物 — 只做一件事，只验收一件事
2. 验收可量化 — 条件具体到操作步骤，不是"看起来不错"
3. 体量可控 — 预计 1-2 个工作周期完成，超过则继续拆
4. 独立可测 — 不依赖未完成的其他 Task

判断示例：

• ❌ "实现农场系统" → 这是 Epic，不是 Task
• ❌ "优化页面" → 没有验收标准
• ❌ "完成种植和收获" → 两件事，应拆两个 Task
• ✅ "实现 7 块农田网格布局，点击地块高亮"
• ✅ "接入 Google OAuth，登录后显示用户头像"

→ 更多拆解指导见 references/breakdown-guide.md

角色工作流

详细操作流程按角色拆分，按需加载：

• PM（产品经理）：references/pm-workflow.md — 规划、拆解、派发、验收、结案
• Dev（开发工程师）：references/dev-workflow.md — 接收、评估、执行、交付

与团队协作协议的关系

本 skill 管"做什么"：层级、拆解、模板、文档结构。 团队协作协议（如 agent-team-orchestration）管"怎么协作"：状态流转、交接协议、评审规则。 两者互补，不重叠。