菜单
File implementation work on the Conveyor factory — single tasks or dependency-ordered task sets — via the MCP create_task tool, in the house style the factory's agents implement and review well. Use when the operator says to file a task, a fix wave, or a phase's work breakdown.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/kidus-tiliksew/conveyor --skill conveyor-file-tasks命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
File implementation work on the Conveyor factory — single tasks or dependency-ordered task sets — via the MCP create_task tool, in the house style the factory's agents implement and review well. Use when the operator says to file a task, a fix wave, or a phase's work breakdown.
Draft and push Conveyor planning documents from a local session — requirements (v2 REQ→AC), System Design documents, DEC-n decision records, and product-overview uploads — over the factory's REST API with the propose→confirm discipline intact. Use when the operator wants to plan features, write or revise any document tier, promote an overview claim into a requirement, or record a decision, without using the in-product planning chat.
Create or revise a testing-strategy System Design document for a project or repository scope by discovering its real verification surfaces, evidence boundaries, and known gaps first.
| name | conveyor-file-tasks |
| description | File implementation work on the Conveyor factory — single tasks or dependency-ordered task sets — via the MCP create_task tool, in the house style the factory's agents implement and review well. Use when the operator says to file a task, a fix wave, or a phase's work breakdown. |
Read and follow docs/playbooks/conveyor-task-filing.md — the canonical, tool-neutral playbook (body house style, boundaries, exit criteria, dependency ordering).
Non-negotiables, restated: phase-sized work is never one task — file a
dependency-ordered set; siblings declare file ownership and migration-
number starts; no acceptance criterion may require an operator-only act
(use checkpoint phrasing instead). The confirmed factory document corpus is
the authority: cite confirmed REQ-n/AC-n.m, DEC-n, and governing System Design
document names or IDs. Every normative document change remains a proposal for
operator confirmation. For web-only work, allow the DEC-16 generated
internal/httpapi/dashboard bundle rather than banning internal/**; if
implementation discovers an approved-plan conflict, require the operator-gated
request_plan_revision path rather than an acceptance-criteria exception.