Skill

create-task

Create a One Horizon personal task or roadmap initiative when the user explicitly asks for that exact record type and the scope is already clear. Prefer task-management for ambiguous or multi-step operational requests. For bugs or feature requests, use report-issue instead. Requires One Horizon MCP.

npx claudepluginhub onehorizonai/skills --plugin one-horizon

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Create a new personal task or roadmap initiative.

Supporting Assets

agents/openai.yamlassets/logo.svg

SKILL.md

Similar Skills

secondbrain-task

Creates sequential tasks with priority, status, due dates in secondbrain's .claude/data/tasks YAML shards. Activates on 'create task', 'add todo', or similar requests.

1 file

secondbrain

teamwork-task-creator

Creates formatted Teamwork tasks from user descriptions of bugs, QA handoffs, epics, or little tasks, using context-aware template selection for web dev project tracking.

4 files

cms-cultivator

using-superpowers

185.1k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Stars2

Forks1

Last CommitApr 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Create Task

Create a new personal task or roadmap initiative.

Work type boundary

Initiative: use for roadmap-first planned work that should tie back to product goals, releases, components, or team progress.
Personal task: use for simple personal follow-up that only the owner needs to track.
Do not use this skill to guess between initiative, bug, ongoing work, and personal task from a vague request. Use task-management for that.
Do not use personal tasks as a substitute for roadmap work.
If the user needs help writing or structuring the initiative first, use initiative-brief.

Instructions

Personal task

Call create-todo for personal follow-up work. Use initiativeId to link it back to a roadmap initiative via PART_OF relation when the personal task represents a delivered slice of initiative work:

create-todo({
  "title": "Implement HubSpot OAuth callback handler",
  "description": "Handle auth code exchange and token persistence",
  "status": "Planned",
  "workspaceId": "<workspaceId>",
  "initiativeId": "<initiativeId>"
})

For completed implementation write-back, create the personal task then add a comment with what changed:

create-todo({
  "title": "Implemented HubSpot lead sync auth + sync",
  "status": "Completed",
  "workspaceId": "<workspaceId>",
  "initiativeId": "<initiativeId>"
})

add-task-comment({
  "taskId": "<newTaskId>",
  "source": "skill",
  "comment": "**Changes**\n- What changed: Built OAuth callback flow, sync worker, and retry handling\n- Why: Enable stable end-to-end HubSpot lead sync flow"
})

Roadmap initiative

Call create-initiative for planned product work that belongs on the roadmap. Supports parentInitiativeId and taxonomyLabelIds:

create-initiative({
  "title": "Build HubSpot lead sync integration",
  "description": "OAuth, sync jobs, task mapping, and observability",
  "status": "Open",
  "workspaceId": "<workspaceId>",
  "assigneeIds": ["<userId>"],
  "teamIds": ["<teamId>"],
  "parentInitiativeId": "<parentInitiativeId>",
  "taxonomyLabelIds": ["<labelId>"]
})