Skip to main content
skill CX Codex

10-task — Claude Code skill: what it does, how to install

10-task — a skill that takes one bounded backlog task through framing, review and a final save. Reach for it when a piece of delivery work needs writing down, linking, ordering or closing.

MIT ★ 571 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-pm@aidd-framework
Open on GitHub

What 10-task does

The skill handles one narrow thing: a backlog Task for delivery work that carries no value of its own for the user. Three steps do the job. frame states the task, review questions whether it really is a Task and whether it can be picked up, finalize writes it down or changes its state. A task already in the tracker jumps straight to that last step.

Only the file for the next action gets read, so the context stays small. Product calls and lifecycle calls stay with you, and the skill keeps evidence, decisions and guesses apart. Source links and edits you already made survive the run, and the questions it asks sound like ordinary conversation rather than step names.

Nothing gets written without your explicit go-ahead. User Stories, Spike, defects and the implementation itself sit outside its scope, so it will not stretch a Task to cover them. Input is either a request in plain words or a task that exists already.

What it helps with

  • turn a verbal request into a backlog task
  • check that an item is a Task and not a User Story
  • move a task to another status without silent writes
  • keep the source link attached to the task
  • order and estimate tasks before someone picks them up

Example prompts for the agent

  • Create a backlog Task from this request: fix retries in the client module, keep it to one piece of work
  • Review TASK-142 and tell me whether it is ready to start
  • Move TASK-142 to in progress — this message is my approval

How to install 10-task

1Plugin marketplace

/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-pm@aidd-framework

This installs the whole aidd-pm plugin with all its skills

2Skills CLI (Vercel)

npx skills add ai-driven-dev/framework --skill 10-task -a claude-code

3Manually: put the files in place

~/.claude/skills/10-task/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/10-task/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 10-task

How do I install 10-task in Claude Code?

Use the marketplace: /plugin marketplace add ai-driven-dev/framework first, then /plugin install aidd-pm@aidd-framework. The other route is npx skills add ai-driven-dev/framework --skill 10-task -a claude-code.

What does 10-task do?

It frames a single delivery task, challenges its type and readiness, then saves it or transitions it. Product and lifecycle decisions stay with you.

What is 10-task not meant for?

User Stories, Spike, defects and implementation. The skill records delivery work; it does not plan it or write code.

Source text

SKILL.md · MIT
---
name: 10-task
description: Produces or refines a backlog Task for bounded delivery work without independent user value. Use when the user wants to create, link, order, estimate, transition, or complete one. Not for User Stories, Spikes, Defects, or implementation.
argument-hint: request | task
---

# Task

```mermaid
flowchart LR
  source([request or Task]) --> frame --> review --> finalize
  source -->|"already persisted"| finalize
  review -->|"revise"| frame
  finalize -->|"revise"| frame
  finalize -->|"authorized"| done([Task])
```

## Actions

Run the flow above. Read only the next action file.

| Action | Does |
| --- | --- |
| frame | define one bounded delivery Task |
| review | challenge its type and readiness |
| finalize | persist or transition the Task |

## Transversal rules

- Keep product and lifecycle decisions with the user.
- Separate evidence, decisions, and assumptions.
- Preserve source links and existing edits.
- Ask natural questions; never expose actions, references, or unchanged state.
- Require explicit approval or caller-provided bounded authority before any write.
- Record delivery work; never plan or implement it.

© AI-Driven Dev · MIT · ai-driven-dev/framework

Similar skills

All skills for Notes, tasks and projects →

From the same set80

The whole set →
1-documentation The 1-documentation rule guides edits to project Markdown: it keeps decisions and useful commands while removing repetition and temporary records. It applies to selected files and folders. CX Codex +1 ★ 571repo stars 03-prd 03-prd turns a need, idea or brainstorm into a structured product requirements document: a draft from a template, saved only once you approve it. CX Codex +1 ★ 571repo stars 08-three-amigos 08-three-amigos evaluates epics and user stories through product, delivery, or quality perspectives, then reconciles three separate reports before backlog edits. CX Codex +1 ★ 571repo stars 10-learn 10-learn — a skill for Claude Code, Cursor, and other platforms that records decisions, conventions, lessons, and code review findings as durable project knowledge. CX Codex +1 ★ 571repo stars 05-review 05-review inspects git diffs or implementation plans to confirm changes are ready to ship, pairing every issue with a fix. CX Codex +1 ★ 571repo stars 01-brainstorm The 01-brainstorm skill clarifies a rough idea through questions, then turns the discussion into a short brief. Use it when a request is ambiguous or you want to explore an idea together. CX Codex +1 ★ 571repo stars 3-cli-process 3-cli-process sets the conventions for a CLI process: how it shuts down, which channel gets which output, and what exit code it returns. CX Codex +1 ★ 571repo stars 02-project-memory 02-project-memory reads codebase architecture and decisions to build project memory and hook it into AI assistants. Useful for initial setups and drift audits. CX Codex +1 ★ 571repo stars

Project sponsors

Companies that keep this analytics open