菜单
Recap shipped, planned, and blocked work in One Horizon for a person or team. Use for "my recap", "team recap", "team status", "what have I done and what's next", or "what is everyone working on". Requires One Horizon MCP.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Draft release notes for external customers, internal teams, or stakeholders. Use when asked to "write release notes", "draft changelog", "prepare what's new", "summarize this release", or "announce this version". Defaults to external customer-facing copy that excludes internal jargon. Optionally pulls shipped work from One Horizon. Requires One Horizon MCP when sourcing content from workspace data.
Draft a structured initiative brief for roadmap-first planned work in One Horizon. Use for "write an initiative", "draft an initiative brief", "plan this initiative", or "scope this roadmap work". Requires One Horizon MCP.
Create a One Horizon bug or feature request when work type is clear. Use for "log a bug", "file a feature request", or "report this issue". Prefer one-task-management for ambiguous requests. Requires One Horizon MCP.
Turn open bugs into prioritized triage notes. Use when asked "prepare bug triage", "summarize open bugs", or "prioritize defects for review". Requires One Horizon MCP.
Create a One Horizon Todo or roadmap initiative when the user asks for that exact work type and the scope is clear. Prefer one-task-management for ambiguous or multi-step operational requests. For bugs or feature requests, use one-report-issue instead. Requires One Horizon MCP.
Resolve One Horizon team, member, workspace, and identity context. Use when asked "who is on my team", "find Jane's user ID", "which workspace am I in", "list my workspaces", or "who am I". Prefer one-task-management when team or workspace lookup is only one step in a larger operational request. Requires One Horizon MCP.
| name | one-work-recap |
| description | Recap shipped, planned, and blocked work in One Horizon for a person or team. Use for "my recap", "team recap", "team status", "what have I done and what's next", or "what is everyone working on". Requires One Horizon MCP. |
Fetch consolidated recap data for a person or team.
Call my-work-recap:
my-work-recap({ "includeInitiatives": true })
With date range:
my-work-recap({
"startDate": "2024-01-20T00:00:00Z",
"endDate": "2024-01-26T23:59:59Z",
"includeInitiatives": true
})
Call team-work-recap:
team-work-recap({ "teamId": "<teamId>", "includeInitiatives": true })
With date range:
team-work-recap({
"teamId": "<teamId>",
"startDate": "2024-01-20T00:00:00Z",
"endDate": "2024-01-26T23:59:59Z",
"includeInitiatives": true
})
Recap order prioritizes roadmap work first, then bugs, then Todos.
Recap/list output may omit descriptions; call get-task-details for any task that needs deeper context.