How do I install the Ccc Tasks skill?

Run npx skillmds@latest add kevinzai/ccc-tasks in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ccc Tasks safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ccc Tasks?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ccc Tasks free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ccc Tasks?

KevinZai (@kevinzai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ccc Tasks by kevinzai — Agent Skill

Name: Ccc Tasks
Author: KevinZai

File contents

/ccc-tasks — Markdown Task Tracking

The simplest thing that could possibly work. One file. Markdown checkboxes. That's it.

When to use

Personal projects that don't need Linear/Jira
Side-session tracking while a larger Linear ticket is in flight
Brainstorm capture before picking 1-2 to execute
A visible, pushable-to-git audit trail of what happened

Not for

Team coordination with 2+ humans → use /ccc-linear
Long-term project milestones → use Linear project
Sub-tasks of a complex feature → use the feature's spec doc + todo tool

File format

tasks/todo.md in project root:

# Todo

## Active

- [ ] P0 · Ship beta.11 (push + dogfood)
- [ ] P1 · Wire release.yml npm publish
- [x] P0 · Fix --mcp.json silent MCP failures ✅ 2026-04-23

## Blocked

- [ ] P1 · Product Hunt launch — waiting on K13 screencast

## Someday

- [ ] VSCode companion extension
- [ ] Commander Hub user-submitted skills

Priorities: P0 (this week), P1 (this month), P2 (quarter), P3 (someday).

Status: [ ] todo · [x] done (with date) · [~] in progress · [!] blocked.

Process

Session start: read tasks/todo.md → suggest the top 1-2 P0 items to tackle
Pick one: move to "Active" if not already, mark [~], announce scope
Mid-work: leave notes in-line under the task (indented)
Session end: mark [x] with date (or flip to [!] with blocker note), update file
Weekly: prune Done section; archive older than 30d to tasks/archive/YYYY-MM.md

Integration

Append to file — never overwrite (avoid mid-session state loss)
Commit each change — the diff IS the audit trail
Link from CLAUDE.md: See tasks/todo.md for active work

Depends on

Write access to tasks/todo.md (create if missing)
Git for history (optional but recommended)

Adapted from knowledge-work-plugins/productivity/task-management under Apache-2.0 license. Reframed around CC Commander priority conventions (P0-P3).

⚙️ Fable contract: plan before build · verifier ≠ worker · prove before alarm · loops need gates · leave durable state — rules/fable-method.md

---name: ccc-tasksdescription: Lightweight markdown task tracking via tasks/todo.md. Simple format — checkboxes, priorities, status. No database, no service, no sync. Every session start reads…---# /ccc-tasks — Markdown Task TrackingThe simplest thing that could possibly work. One file. Markdown checkboxes. That's it.## When to use- Personal projects that don't need Linear/Jira- Side-session tracking while a larger Linear ticket is in flight- Brainstorm capture before picking 1-2 to execute- A visible, pushable-to-git audit trail of what happened## Not for- Team coordination with 2+ humans → use /ccc-linear- Long-term project milestones → use Linear project- Sub-tasks of a complex feature → use the feature's spec doc + todo tool## File format`tasks/todo.md` in project root:```markdown# Todo## Active- [ ] P0 · Ship beta.11 (push + dogfood)- [ ] P1 · Wire release.yml npm publish- [x] P0 · Fix --mcp.json silent MCP failures ✅ 2026-04-23## Blocked- [ ] P1 · Product Hunt launch — waiting on K13 screencast## Someday- [ ] VSCode companion extension- [ ] Commander Hub user-submitted skills```Priorities: **P0** (this week), **P1** (this month), **P2** (quarter), **P3** (someday).Status: `[ ]` todo · `[x]` done (with date) · `[~]` in progress · `[!]` blocked.## Process1. **Session start:** read `tasks/todo.md` → suggest the top 1-2 P0 items to tackle2. **Pick one:** move to "Active" if not already, mark `[~]`, announce scope3. **Mid-work:** leave notes in-line under the task (indented)4. **Session end:** mark `[x]` with date (or flip to `[!]` with blocker note), update file5. **Weekly:** prune Done section; archive older than 30d to `tasks/archive/YYYY-MM.md`## Integration- Append to file — never overwrite (avoid mid-session state loss)- Commit each change — the diff IS the audit trail- Link from CLAUDE.md: `See tasks/todo.md for active work`## Depends on- Write access to `tasks/todo.md` (create if missing)- Git for history (optional but recommended)---Adapted from `knowledge-work-plugins/productivity/task-management` under Apache-2.0 license. Reframed around CC Commander priority conventions (P0-P3).---> ⚙️ **Fable contract:** plan before build · verifier ≠ worker · prove before alarm · loops need gates · leave durable state — `rules/fable-method.md`

Frequently asked questions

Ccc Tasks