requirement-intake
Skill2 starsChanged 9 months agoMITView on GitHub
负责引导用户按统一入口规范提交需求，生成并维护 primary 需求文件，达到启动门禁后交给 planner-ops 拆解执行。
2 other projects use a version of this.
Adopted by
Most recently taken up by
- themusecatcher/ai-coding-kittheir own version, first seen Sep 15, 2026
- digitaldreams/tuhintheir own version, first seen Jul 6, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- digitaldreams/tuhin★ 3same name
- themusecatcher/ai-coding-kit★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- agent-orchestratorSkill
- audit-guardSkill
- governance-configSkill
- keeperSkill
- planner-coreSkill
- planner-opsSkill
- scheduler-opsSkill
- tester-ephemeralSkill
- worker-deliverySkill
The file
Files
Requirement Intake
核心职责
- 作为用户需求入口代理，收集并标准化任务需求。
- 将用户自然语言需求转换为结构化
primary.md。 - 校验需求完整性并给出缺失项补全提示。
- 管理启动门禁状态：
DRAFT -> READY -> STARTED。 - 在
READY且收到启动指令后，将需求移交给 planner-ops。
输入文件相对路径
- 用户需求输入：会话输入（自然语言）。
- planner 当前配置：
templates/coordination/planner/config/current.md。 - planner 属性配置：
templates/coordination/planner/properties.md。 - 入口需求运行文件：
$AGENT_ORCHESTRATOR_STATE_DIR/planner/primary.md（默认~/.openclaw-state/agent-orchestrator/planner/primary.md）；示例模板：templates/coordination/planner/primary.example.md。
输出文件相对路径
- 入口需求运行文件：
$AGENT_ORCHESTRATOR_STATE_DIR/planner/primary.md（默认~/.openclaw-state/agent-orchestrator/planner/primary.md）；示例模板：templates/coordination/planner/primary.example.md。 - 入口校验记录：
templates/coordination/planner/primary_validation.md。 - 需求澄清问答记录：
templates/coordination/planner/primary_clarifications.md。 - 启动治理联动记录：
templates/coordination/planner/primary_start_governance.md。
读取文件相对路径
- 读取运行态
primary.md（默认~/.openclaw-state/agent-orchestrator/planner/primary.md）判断当前状态与缺失字段；格式参考templates/coordination/planner/primary.example.md。 - 读取
templates/coordination/planner/config/current.md获取约束策略。 - 读取
templates/coordination/planner/properties.md获取执行属性。
入口需求规范
- 每条需求必须具备：
primary_id、title、scope、constraints、acceptance_criteria、priority、status、start_signal。 scope必须明确 in-scope/out-of-scope，不允许仅写目标不写边界。acceptance_criteria必须可测试、可判定，避免主观描述。constraints必须覆盖安全、合规、时间或资源限制。start_signal仅接受NO或YES，为YES时才允许进入 STARTED。
启动门禁流程
- 初次录入需求时写入
DRAFT。 - 若字段缺失，生成
primary_validation.md并在primary_clarifications.md记录补充问题。 - 字段齐全后将状态更新为
READY。 - 收到明确启动指令且
start_signal=YES后，先生成启动治理联动记录（含approval_id、audit_ref）。 - 启动治理联动记录写入成功后，方可更新为
STARTED。 - 进入
STARTED后将任务交给 planner-ops，不再改动核心字段。
路径描述
- 入口需求运行路径：
$AGENT_ORCHESTRATOR_STATE_DIR/planner/primary.md（默认~/.openclaw-state/agent-orchestrator/planner/primary.md）。 - 校验记录路径：
templates/coordination/planner/primary_validation.md。 - 澄清记录路径：
templates/coordination/planner/primary_clarifications.md。 - 启动治理联动记录路径：
templates/coordination/planner/primary_start_governance.md。
命名示例
primary_id示例：primary_20260212_170000。- 校验记录示例：
primary_validation.md。 - 澄清记录示例：
primary_clarifications.md。 - 启动治理联动记录示例：
primary_start_governance.md。
输出文件内容格式
templates/coordination/planner/primary.example.md示例内容格式（运行态文件位于仓外状态目录）：
|---|---|---|---|---|---|---|---|templates/coordination/planner/primary_validation.md文件内容格式：
|---|---|---|---|---|---|templates/coordination/planner/primary_clarifications.md文件内容格式：
|---|---|---|---|---|templates/coordination/planner/primary_start_governance.md文件内容格式：
|---|---|---|---|---|---|---|---|Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.