Skip to content
Back to skills

Subtasks

ASecurity

Strip every reference to the `done:` subtask field from the `documentation-guide` skill — **completely, as if it never existed.** Do **not** relabel it "legacy" and do **not** leave a "this used to exist" note: any mention (even a deprecation note) still costs an agent context on every read, which is the whole reason to remove it. `state:` is the sole canonical field.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 29, 2026
ai-agentsdocumentation

Works with

  • cli

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned September 29, 2026

npx -y skills add sidhanthapoddar99/agent-knowledge-system --skill subtasks --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Subtasks?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Subtasks
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sidhanthapoddar99-subtasks-b02a0387/badge)](https://www.skillsdirectory.com/skills/sidhanthapoddar99-subtasks-b02a0387)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
title: Remove the `done:` field from the skill entirely
status: done
---

Strip every reference to the `done:` subtask field from the `documentation-guide` skill —
**completely, as if it never existed.** Do **not** relabel it "legacy" and do **not** leave a
"this used to exist" note: any mention (even a deprecation note) still costs an agent context
on every read, which is the whole reason to remove it. `state:` is the sole canonical field.

## Where it appears (confirmed)

- **`references/layouts/issues/23_subtasks.md`** — the field is currently prescribed as
  *standard*:
  - the frontmatter example block (`done: false` / `done: true`),
  - the line "`done: true` should be paired with `state: closed` (or `review`)",
  - "Write the file with the standard frontmatter (`title`, `done: false`, `state: open`)",
  - the helper note "flips `state` *and* syncs `done:`".
  → Rewrite all of these to use **`state:` only**. The standard subtask frontmatter becomes
  `title:` + `state:` (no `done:`).
- **`references/layouts/issues/41_searching.md`** — "state vs legacy `done`" and "Subtask
  flips also sync `done:`". → Remove the `done` clauses; the CLI just sets `state`.

## Scope guard

- Sweep **both** skills (`documentation-guide` + `doc-agent`) and **all** reference files for
  the field, but **do not** touch natural-language uses of the word "done" — e.g. "what done
  means", "done-when", "Implementation is done from your perspective", "carry state
  (open/done)". Those are prose, not the field.
- This subtask is **skill text only**. The framework code (`040`) and the migration that
  rewrites existing content (`030`) are separate.

## Verify

- `grep -rn "done:" references/ SKILL.md` (both skills) returns no *field* hits.
- `bun run build` green; `check-skill-links.mjs` clean.

Files in this skill

  • 010_remove-done-from-skill.md1.8 KB
  • 020_migration-convention-and-reference.md2.3 KB
  • 030_done-to-state-migration-script.md1.9 KB
  • 040_remove-done-from-framework-code.md2.1 KB
  • 050_bump-plugin-version.md645 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…