From one-horizon
Run the full loop from planned work or reported bugs to shipped work and write-back in One Horizon. 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.
npx claudepluginhub onehorizonai/skills --plugin one-horizonThis skill uses the workspace's default tool permissions.
Run work execution with strict sequencing and explicit write-back.
Resumes unfinished GitHub tasks such as handovers, incomplete grills, and mid-draft writing via /pickup command. Claims issues interactively from Ready list or directly by number.
Manages backlog items through grooming, planning, and closure using GitHub Issues, Projects, Milestones. Interactive browser, auto-mode, resolve/close with evidence, SAM integration.
Guides MCP work item role transitions: identifies by UUID/title, checks gate status/missing notes/guidance, suggests advance triggers like start/complete/block/cancel.
Share bugs, ideas, or general feedback.
Run work execution with strict sequencing and explicit write-back.
add-task-comment instead.patch-document with workspaceId, taskId set to the initiative ID, and precise ops; the server resolves or creates the linked content document automatically.replace_text, insert_before, insert_after, and delete_text over rewriting the entire description.update-initiative only for initiative metadata: title, status, assigneeIds, teamIds, taxonomyLabelIds, and parentInitiativeId.patch-document(taskId=initiativeId, ...) first, then update-initiative(...). If refreshed full details are needed after editing, call get-task-details.get-task-details, then retry with corrected ops."source": "skill" when calling add-task-comment so comments are tagged with their origin.Changes/Why comments only when real delivery happened (bug fix, completed personal task, completed initiative work).Update comment instead.list-planned-work, list-initiatives, or list-bugs).get-task-details.update-* or create-todo) and add comments via add-task-comment.If the agent is in plan mode, or the user asks for a plan, include workflow tasks from this skill in the plan explicitly.
Required plan items:
get-task-details.update-* or create-todo) and add a comment with progress notes.For "Fix all bugs assigned to me", include per-bug execution/write-back steps. For initiative implementation prompts, include initiative matching + confirmation before coding.
When a user asks to implement a bug, initiative, or personal task, run the full flow and do not treat it as a status-only update.
Required sequence:
list-bugs, list-initiatives, list-planned-work).get-task-details for each selected task before implementation.bug-triage-prep, initiative-summary, recap/summarizer skills) before coding or writing updates.update-* or create-todo, then add a comment via add-task-comment after each completed chunk.If any required step is skipped, the run is incomplete.
If implementation happened, the write-back must include a **Changes** block with both "What changed" and "Why".
Use this exact sequence:
list-my-teams to resolve user/team context.list-bugs filtered to current user assignee and active statuses.get-task-details.update-bug with latest status, then add-task-comment with fix notes.update-bug with status and add-task-comment with blocker details.Required add-task-comment content after update-bug:
Use this exact sequence:
list-initiatives with active statuses.get-task-details for selected initiative, then use Goals, Products, and labelsByType to verify fit.create-todo using status: "Completed" and initiativeId as soon as implementation is done.update-initiative if status/progress should advance.If the initiative description also needs edits:
patch-document with workspaceId, taskId, and targeted ops.update-initiative only for metadata changes.get-task-details and retry with corrected ops.get-task-details after the mutations if you need the refreshed initiative body.create-todo write-back shape:
create-todo({
"title": "Implemented HubSpot lead sync integration",
"description": "Added OAuth flow, sync job, and mapping logic. Validated with integration tests.",
"status": "Completed",
"initiativeId": "<initiativeId>",
"workspaceId": "<workspaceId>"
})
list-initiatives.initiativeId and add extra links with relation tooling.When reporting progress back to the user, use this structure:
Target: which task is being processedAction: what was changedWrite-back: which MCP tool was called and what was updatedLinks: initiative IDs connectedUse add-task-comment for all progress notes. Never modify task descriptions.
Delivery comment (code shipped / fix completed / task completed):
**Changes**
- What changed: <short summary>
- Why: <root cause or goal>
Research or planning comment (no external implementation delivered):
## Update
- Summary: <what was researched/decided/triaged>
get-task-details before proceeding.get-task-details output (Goals, Products, labelsByType) before deciding initiative linkage.Before declaring completion to the user, verify all completed tasks were updated in One Horizon:
update-bug called with final status + add-task-comment with **Changes**.update-todo called with final status + add-task-comment with **Changes**, or create-todo created as Completed + comment.update-initiative called with status + add-task-comment with progress notes.If any completed item is missing write-back, stop and perform the update first.
A run is complete only when all are true: