Agent skill
ln-301-task-creator
Creates implementation, refactoring, and test tasks from templates. Use when an approved task plan needs tasks created in Linear and kanban.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/ln-301-task-creator-levnikolaevich-claude-code-skills-2
SKILL.md
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.
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 shared/references/coordinator_summary_contract.md and shared/references/task_plan_worker_runtime_contract.md
MANDATORY READ: Load shared/references/environment_state_contract.md, shared/references/storage_mode_detection.md, shared/references/template_loading_pattern.md, shared/references/creation_quality_checklist.md, and shared/references/destructive_operation_safety.md
Inputs
Core inputs:
taskTypestoryDataidealPlan— task list with scopes, AC mappings, dependencies, layer classificationsteamIdguideLinks
Coordinator context (passed in ADD/CREATE mode):
traceabilityTablePath— materialized traceability table from coordinator Phase 2discoveryContext— architecture, tech stack, key files, integration points from coordinator Phase 1tasksToCreate— specific tasks to create (ADD mode). Worker writes the 7-section document, does not decide whether tasks are needed.
Transport inputs:
- standalone: omit
runIdandsummaryArtifactPath - managed: pass both
runIdandsummaryArtifactPath
Runtime
Runtime family: task-plan-worker-runtime
Phase profile:
PHASE_0_CONFIGPHASE_1_LOAD_INPUTSPHASE_2_LOAD_CONTEXTPHASE_3_GENERATE_TASK_DOCSPHASE_4_VALIDATE_TASKSPHASE_5_CONFIRM_OR_AUTOAPPROVEPHASE_6_APPLY_CREATEPHASE_7_UPDATE_KANBANPHASE_8_WRITE_SUMMARYPHASE_9_SELF_CHECK
Summary artifact rules:
- emit
summary_kind=task-plan - standalone runs generate their own
run_idand write the default worker-family artifact path - managed runs require both
runIdandsummaryArtifactPathand 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:
shared/references/coordinator_summary_contract.mdshared/references/task_plan_worker_runtime_contract.md
Payload fields:
modestory_idtask_typetasks_createdtasks_updatedtasks_canceledtask_urlskanban_updateddry_warnings_countwarnings
Always write the validated summary before terminal outcome.
Workflow
- Resolve task provider and template set.
- Run DRY and destructive-operation checks where applicable.
- 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. - Select scope:
ADD: usetasksToCreateonlyCREATE: expand the fullidealPlan
- Generate task documents from the selected scope.
- Validate type-specific rules.
- Show preview and get confirmation if needed.
- Create tasks in Linear or file mode.
- Update kanban.
- 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:tasksToCreateis the execution scope. Do not re-expand the full ideal plan when the coordinator already selected the delta. - STOP before save_issue: 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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?