creates draft task file in .specs/tasks/draft/ with original user intent

GPL-3.0Auto-check passed

Install Add Task

skills CLI
$ npx skills add NeoLabHQ/context-engineering-kit --skill add-task -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NeoLabHQ/context-engineering-kit add-task --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NeoLabHQ/context-engineering-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/add-task .claude/skills/add-task && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
add-task
GitHub stars
1.7k
Token cost
~1.5k tokens
SKILL.md length
525 words
Files
1
Skills in repo
57
Repo updated
First seen
Licence
GPL-3.0

At a glance

creates draft task file in .specs/tasks/draft/ with original user intent

  • Works in 5 steps: Ensure Directory Structure → Analyze Input → Structure the Task → …
  • SKILL.md covers Role, Goal, Input and Instructions, plus 4 more sections
  • Calls bash

What it does

Add Task is an agent skill from NeoLabHQ/context-engineering-kit. creates draft task file in .specs/tasks/draft/ with original user intent

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Hand-crafted Claude Code Skills focused on improving agent results quality. Compatible with OpenCode, Cursor, Antigravity, Gemini CLI, and others. Includes CodeRabbit open-source… The licence is GPL-3.0.

Example prompts

  • “Use the add-task skill to create draft task file in .specs/tasks/draft/ with original user intent”
  • “/add-task”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Ensure Directory Structure
  2. Analyze Input
  3. Structure the Task
  4. Generate File Name
  5. Create Task File

What it can do on your machine

Read from SKILL.md and the folder at commit 23e2428. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Add Task loads about 1.5k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 525 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~20
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NeoLabHQ/context-engineering-kit at commit 23e2428, republished under its GPL-3.0 licence (© NeoLabHQ). 525 words, ~1,502 tokens.

Download SKILL.mdSave it as .claude/skills/add-task/SKILL.md (or your agent's skills folder).
name
add-task
description
creates draft task file in .specs/tasks/draft/ with original user intent

Create Draft Task File

Role

Your role is to create a draft task file that exactly matches the user's request.

Goal

Create a task file in .specs/tasks/draft/ with:

  • Clear, action-oriented title (verb + specific description)
  • Appropriate type classification (feature/bug/refactor/test/docs/chore/ci)
  • Correct dependencies if any
  • Useful description preserving user intent
  • Correct file name

Input

  • User Input: The task description/title provided by the user (passed as argument)
  • Target Directory: Default is .specs/tasks/draft/

Instructions

1. Ensure Directory Structure

Run the folder creation script to create task directories and configure gitignore:

bash
bash ${CLAUDE_PLUGIN_ROOT}/scripts/create-folders.sh

This creates:

  • .specs/tasks/draft/ - New tasks awaiting analysis
  • .specs/tasks/todo/ - Tasks ready to implement
  • .specs/tasks/in-progress/ - Currently being worked on
  • .specs/tasks/done/ - Completed tasks
  • .specs/scratchpad/ - Temporary working files (gitignored)
  • .specs/analysis/ - Analysis of the task
  • .specs/reports/ - Reports of the task

Fallback: if script not found, or there another issue, create folder structure manually and add .specs/scratchpad/ to .gitignore

2. Analyze Input
  1. Parse the user's request:

    • Extract the core task objective
    • Identify implied type (bug, feature, task)
    • List of task files that this task depends on
  2. Clarify if ambiguous (only if truly unclear):

    • Is this a bug fix or new feature?
    • Any related tasks or dependencies? (if not proided, then assume none)
3. Structure the Task
  1. Create action-oriented title:

    • Start with verb: Add, Fix, Update, Implement, Remove, Refactor
    • Be specific but concise
    • Examples:
      • "Add validation to login form"
      • "Fix null pointer in user service"
      • "Implement caching for API responses"
  2. Determine type:

    TypeUse When
    featureNew functionality or capability
    bugSomething is broken or not working correctly
    refactorCode restructuring without changing behavior
    testAdding or updating tests
    docsDocumentation changes only
    choreMaintenance tasks, dependency updates
    ciCI/CD configuration changes
4. Generate File Name
  1. Create short name from the task title:

    • Lowercase the title
    • Replace spaces with hyphens
    • Remove special characters
    • Keep it concise (3-5 words max)
    • Example: "Add validation to login form" -> add-validation-login-form
  2. Form file name: <short-name>.<issue-type>.md

    • Examples:
      • add-validation-login-form.feature.md
      • fix-null-pointer-user-service.bug.md
      • restructure-auth-module.refactor.md
      • add-unit-tests-api.test.md
      • update-readme.docs.md
      • upgrade-dependencies.chore.md
      • add-github-actions.ci.md
  3. Verify uniqueness: Check .specs/tasks/draft/, .specs/tasks/todo/, .specs/tasks/in-progress/, and .specs/tasks/done/ for existing files with same name

Show full SKILL.md (188 more words)Show less
5. Create Task File

Use Write tool to create .specs/tasks/todo/<short-name>.<issue-type>.md:

markdown
---
title: <ACTION-ORIENTED TITLE>
depends_on: <list of task files that this task depends on>
---

## Initial User Prompt

{EXACT user input as provided}

## Description

// Will be filled in future stages by business analyst

Constraints

  • Do NOT invoke the plan skill - the workflow handles subsequent phases
  • Do NOT create files outside .specs/tasks/draft/
  • Do NOT modify existing task files
  • Do NOT write description, only put // ... placeholder as specified in the task file.
  • Do NOT write depends_on section if no dependencies are provided.

Expected Output

Return to the orchestrator:

  1. Task file path: Full path to created file (e.g., .specs/tasks/todo/add-validation-login-form.feature.md)
  2. Generated title: The action-oriented title created
  3. Issue type: task, bug, or feature

Format:

Created task file: .specs/tasks/draft/<name>.<type>.md
Title: <action-oriented title>
Type: <task|bug|feature>
Depends on: <list of task files that this task depends on>

Success Criteria

  • Directories .specs/tasks/draft/, .specs/tasks/todo/, .specs/tasks/in-progress/, .specs/tasks/done/ exist
  • Task file created in .specs/tasks/draft/ with correct naming convention (<name>.<type>.md)
  • File name is unique across all status folders (no overwriting existing files)
  • Depends on section is correct if dependencies are provided
  • Title starts with action verb (Add, Fix, Implement, Update, Remove, Refactor)
  • Type is correctly classified and reflected in file extension (.feature.md, .bug.md, .refactor.md, .test.md, .docs.md, .chore.md, .ci.md)
  • Original user input preserved in "Initial User Prompt" section
  • Description is empty placeholder // Will be filled in future stages by business analyst

Examples

Test task (.specs/tasks/draft/add-unit-tests-auth.test.md):

markdown
---
title: Add unit tests for auth module
---

## Initial User Prompt

add tests for auth

## Description

// Will be filled in future stages by business analyst

Bug with context (.specs/tasks/draft/fix-login-timeout.bug.md):

markdown
---
title: Fix login timeout on slow connections
---

## Initial User Prompt

users getting 504 errors on slow wifi

## Description

// Will be filled in future stages by business analyst

Feature request (.specs/tasks/draft/implement-dark-mode.feature.md):

markdown
---
title: Implement dark mode toggle
---

## Initial User Prompt

add dark mode to settings page

## Description

// Will be filled in future stages by business analyst

© NeoLabHQ, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/add-task of NeoLabHQ/context-engineering-kit.

Open the folder on GitHubat commit 23e2428

Compare with similar skills

Add Task next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Add Task compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add Task this skillNeoLabHQ/context-engineering-kit1.7k—~1.5kAutomated safety check: PassGPL-3.0
Spec Writergarrytan/gstack136k—~14kAutomated safety check: NotesMIT
Specgarden-co/classic-jazz2.5k—~1.3kAutomated safety check: PassMIT
Spec Driven Workflowalirezarezvani/claude-skills28k—~3.9kAutomated safety check: PassMIT
Sparc Specruvnet/ruflo74k—~1.1kAutomated safety check: NotesMIT
Write A Specdifferent-ai/openwork24k—~3.3kAutomated safety check: PassCustom licence

Similar skills

  • Spec Writer

    garrytan/gstack

    Converts a vague idea into a precise, executable spec in five phases, files it as an issue and can start an agent on it in a fresh worktree.

    136k GitHub stars~14k tokensUpdated today
    DevelopmentAuto-check: notes
  • Spec

    garden-co/classic-jazz

    Implement features using Spec Driven Development (SDD) workflow.

    2.5k GitHub stars~1.3k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Spec Driven Workflow

    alirezarezvani/claude-skills

    A skill your agent uses when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first…

    28k GitHub stars~3.9k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Sparc Spec

    ruvnet/ruflo

    Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory

    74k GitHub stars~1.1k tokensUpdated today
    Product & Project ManagementAuto-check: notes
  • Write A Spec

    different-ai/openwork

    Write or extend an E2E journey spec in evals/specs that proves a PR's change to a human reviewer.

    24k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed
  • To Spec

    vinvcn/mattpocock-skills-zh-CN

    把当前对话转成 spec 并发布到项目 issue tracker:不做访谈,只综合已经讨论的内容. An agent skill from vinvcn/mattpocock-skills-zh-CN.

    4.7k GitHub stars~441 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from NeoLabHQ/context-engineering-kit

All 57 skills in this repo
  • Git Notes

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides…

    1.7k GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Load PR Comments

    NeoLabHQ/context-engineering-kit

    A skill your agent uses to load open/unresolved PR review comments then aggregate them as tasks in .specs/comments/.md for parallel agents to fix.

    1.7k GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Prompt Engineering

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing…

    1.7k GitHub stars~4.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Multi Agent Patterns

    NeoLabHQ/context-engineering-kit

    Design multi-agent architectures for complex tasks. An agent skill from NeoLabHQ/context-engineering-kit.

    1.7k GitHub starsUsed in 6 repos~6k tokens
    Auto-check passed
  • Review PR

    NeoLabHQ/context-engineering-kit

    Review an existing GitHub pull request and post inline review comments on its diff.

    1.7k GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Subagent Driven Development

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or…

    1.7k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Add Task

What does Add Task do?

creates draft task file in .specs/tasks/draft/ with original user intent. Add Task is an agent skill from NeoLabHQ/context-engineering-kit.

How do I install Add Task in Claude Code?

Run `npx skills add NeoLabHQ/context-engineering-kit --skill add-task -a claude-code`. Or copy the skill folder (skills/add-task in NeoLabHQ/context-engineering-kit) into .claude/skills/add-task in your project. Claude Code loads it when a task matches its description.

How do I install Add Task in Codex?

Run `npx skills add NeoLabHQ/context-engineering-kit --skill add-task -a codex`. Or copy the skill folder (skills/add-task in NeoLabHQ/context-engineering-kit) into .agents/skills/add-task in your project. Codex loads it when a task matches its description.

Can I use Add Task in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NeoLabHQ/context-engineering-kit --skill add-task -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-task, .gemini/skills/add-task, .github/skills/add-task and .opencode/skills/add-task in your project.

What does Add Task need to run?

Going by SKILL.md and its folder, Add Task needs the command-line tools its instructions call (bash).

Does Add Task access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Add Task safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Add Task use?

Add Task is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Add Task use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Add Task?

Skills that share tags, products or a category with Add Task: Spec Writer (garrytan/gstack, 136k stars), Spec (garden-co/classic-jazz, 2.5k stars), Spec Driven Workflow (alirezarezvani/claude-skills, 28k stars) and Sparc Spec (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Task?

NeoLabHQ (a GitHub organization) maintains it in NeoLabHQ/context-engineering-kit, which has 1,749 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on August 26, 2026.

Source: NeoLabHQ/context-engineering-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.