Task Creator
Creates implementation, refactoring, and test tasks from templates. Use when an approved task plan needs tasks created via the configured tracker provider and reflected in kanban.
MCP get_skill({ skillId: "task-creator-3dd909be" })Use this skill with your agent
Create a free account and connect via MCP
> **Paths:** File paths (`references/`, `../ln-*`) are relative to this skill directory. # Task Creator **Type:** L3 Worker **Category:** 3XX Planning Standalone-first worker for task creation. It creates tasks from an already approved plan and returns a stable summary contract. **MANDATORY READ:** Load `references/coordinator_summary_contract.md` and `references/task_plan_worker_runtime_contract.md` **MANDATORY READ:** Load `references/environment_state_contract.md`, `references/storage_mode_detection.md`, `references/template_loading_pattern.md`, `references/creation_quality_checklist.md`, and `references/destructive_operation_safety.md` ## Inputs Core inputs: - `taskType` - `storyData` - `idealPlan` — task list with scopes, AC mappings, dependencies, layer classifications - `teamId` - `guideLinks` Coordinator context (passed in ADD/CREATE mode): - `traceabilityTablePath` — materialized traceability table from coordinator Phase 2 - `discoveryContext` — architecture, tech stack, key files, integration points from coordinator Phase 1 - `tasksToCreate` — specific tasks to create (ADD mode). Worker writes the 7-section document, does not decide whether tasks are needed. Transport inputs: - standalone: omit `runId` and `summaryArtifactPath` - managed: pass both `runId` and `summaryArtifactPath` ## Runtime Runtime family: `task-plan-worker-runtime` Phase profile: 1. `PHASE_0_CONFIG` 2. `PHASE_1_LOAD_INPUTS` 3. `PHASE_2_LOAD_CONTEXT` 4. `PHASE_3_GENERATE_TASK_DOCS` 5. `PHASE_4_VALIDATE_TASKS` 6. `PHASE_5_CONFIRM_OR_AUTOAPPROVE` 7. `PHASE_6_APPLY_CREATE` 8. `PHASE_7_UPDATE_KANBAN` 9. `PHASE_8_WRITE_SUMMARY` 10. `PHASE_9_SELF_CHECK` Summary artifact rules: - emit `summary_kind=task-plan` - standalone runs generate their own `run_id` and write the default worker-family artifact path - managed runs require both `runId` and `summaryArtifactPath` and must write the summary to the exact provided path - always write the validated summary artifact before terminal outcome ## Output Contract Always build a structured `task-plan` summary envelope per: - `references/coordinator_summary_contract.md` - `references/task_plan_worker_runtime_contract.md` Payload fields: - `mode` - `story_id` - `task_type` - `tasks_created` - `tasks_updated` - `tasks_canceled` - `task_urls` - `kanban_updated` - `dry_warnings_count` - `warnings` Always write the validated summary before terminal outcome. ## Workflow 1. Resolve task provider and template set. 2. Run DRY and destructive-operation checks where applicable. 3. Use coordinator context (`discoveryContext`, `traceabilityTablePath`) to understand architecture. Research codebase for implementation details (existing patterns, related files, integration points) to write good Technical Approach sections. 4. Select scope: - `ADD`: use `tasksToCreate` only - `CREATE`: expand the full `idealPlan` 5. Generate task documents from the selected scope. 6. Validate type-specific rules. 7. Show preview and get confirmation if needed. 8. Create tasks via the configured tracker provider. 9. Update kanban. 10. Return structured summary. ## Critical Rules - Remain standalone-capable. - Do not require coordinator runtime state. - Keep implementation, refactoring, and test rules separated by `taskType`. - Write machine-readable summary output every time. - **Ideal plan is binding.** Create every task in the approved plan. Do not re-evaluate whether tasks should exist. - **Fast path for `ADD`:** `tasksToCreate` is the execution scope. Do not re-expand the full ideal plan when the coordinator already selected the delta. - **STOP before tracker `createTask`:** verify all 7 sections present in body: Context, Implementation Plan, Technical Approach, Acceptance Criteria, Affected Components, Existing Code Impact, Definition of Done. PreToolUse hook will BLOCK creation without them. ## Definition of Done - [ ] Templates loaded - [ ] Task documents generated - [ ] Type-specific validation passed - [ ] Tasks created in provider-specific storage - [ ] kanban updated - [ ] Structured summary returned - [ ] Summary artifact written to the managed or standalone runtime path --- **Version:** 3.0.0 **Last Updated:** 2025-12-23
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Dev Environment Setup
Installs agents, configures MCP servers, aligns marketplace plugins, creates and audits instructions. Use after setup or when agents/MCP/plugins need alignment.
MCP Configurator
Use when installing MCP packages and configuring Claude-side MCP registration, hooks, permissions, IDE extension mode, and migrations.
Code Knowledge Graph
Builds and queries code knowledge graph for dependency analysis, references, implementations, and architecture overview. Use when starting work on unfamiliar codebase or before refactoring.