skills

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.

Fetch the full details for one known One Horizon task when the task ID is already available and the user needs exact task context. Prefer one-task-management when details are only one step in a larger operational request. Requires One Horizon MCP.

Turn current work into handoff notes a teammate can continue from. Use when asked to "write handoff notes", "prepare transition docs", or "document my current ownership". Requires One Horizon MCP.

Turn initiative data into a concise status update. Use when asked "summarize these initiatives", "give me initiative status", or "prepare initiative update notes". Requires One Horizon MCP.

Look up One Horizon taxonomy labels when the user explicitly asks for label IDs or available goals, companies, products, releases, components, skills, coding tools, or agents. Prefer one-task-management when taxonomy lookup is only one step in a larger operational request. Requires One Horizon MCP.

List planned, shipped, blocked, and open work across One Horizon initiatives, bugs, and Todos. Use when asked "what's on my plate", "what did I ship", "show blockers", "what initiatives are active", "show open bugs", "what should I pick up next", or "what is the team working on". Requires One Horizon MCP.

Create, read, update, and delete standalone workspace documents in One Horizon. Use when asked to "create a spec", "write a requirement doc", "find all documents", "update this document", "delete this doc", or "show document content". For initiative description edits, use patch-document through one-task-management instead. Requires One Horizon MCP.

Turn recent work into an engineering retro with shipped work, patterns, carryover, and next focus. Use when asked to "weekly retro", "what did we ship", "engineering retrospective", "retro this sprint", or "team retro". Proactively suggest at the end of a work week or sprint. Requires One Horizon MCP.

Suggest One Horizon roadmap improvements by reviewing initiatives, planned work, blockers, bugs, and taxonomy. Use when asked "suggest roadmap changes", "improve my roadmap", "what is missing from my roadmap", "review my roadmap", or "should this be an initiative or ongoing work". Requires One Horizon MCP.

Run a literal text search over One Horizon tasks when the user explicitly asks to search by title or indexed content. Prefer one-task-management when search is only one step in a larger operational request. Returns ranked summary hits, not full task details. Requires One Horizon MCP.

Turn recent work into standup talking points for one person or a whole team. Use when asked "prep my standup", "what should I say", "give me my standup update", "team standup summary", or "what should we cover in standup". Requires One Horizon MCP.

Handle operational One Horizon requests that need work lookup, creation, updates, assignment, tagging, comments, or document lookup. Use when asked "mark this done", "assign this", "create a bug", "log a follow-up", "find the task for X", "find the spec for Y", "show comments", or "tag this initiative". Do not use for retros, standups, handoff notes, or stakeholder summaries. Requires One Horizon MCP.

Apply a direct update to known One Horizon work when the target and action are clear, such as changing status, reassigning, adding a comment, or reacting to a comment. Prefer one-task-management for ambiguous or multi-step operational requests. Requires One Horizon MCP.

Run the full loop from planned work or reported bugs to implementation, validation, and One Horizon write-back. Use for prompts like "what do I have planned", "pick this up and implement it", "I found a problem", "fix all bugs assigned to me", "implement HubSpot lead sync", and "write this back to One Horizon". Requires One Horizon MCP.

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.

Turn One Horizon activity into a concise update for a manager, team, or stakeholder. Use when asked to "summarize my work", "write a status report", "create a weekly summary", or "brief my manager". Includes initiatives and blockers when provided. Requires One Horizon MCP.