Stage 3 of the SDD pipeline — turn a ZettelFlow plan (in a GitHub issue comment) into an ordered TDD task checklist posted as a second issue comment.

MITAuto-check passedTesting & QA

Install Tasks

skills CLI
$ npx skills add RafaelGB/Obsidian-ZettelFlow --skill tasks -a claude-code

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

GitHub CLI
$ gh skill install RafaelGB/Obsidian-ZettelFlow tasks --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/RafaelGB/Obsidian-ZettelFlow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/tasks .claude/skills/tasks && 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
tasks
GitHub stars
174
Token cost
~573 tokens
SKILL.md length
282 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Stage 3 of the SDD pipeline — turn a ZettelFlow plan (in a GitHub issue comment) into an ordered TDD task checklist posted as a second issue comment.

  • Tasks that involve Test-driven development
  • SKILL.md covers Owner, Steps, Right-sizing and Quality bar (the stage-3 gate)
  • Calls npm
  • Tasks that involve Task breakdown

What it does

Tasks is an agent skill from RafaelGB/Obsidian-ZettelFlow. Stage 3 of the SDD pipeline — turn a ZettelFlow plan (in a GitHub issue comment) into an ordered TDD task checklist posted as a second issue comment. Each task has the failing test to write first and the guardrail that proves it. Use after a plan comment exists and the user says "break this into tasks", "make the task list", or "tasks for issue

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

It sits in Testing & QA, covering Test-driven development, Task breakdown and Failing and flaky tests. It works with GitHub, Obsidian and npm. The repository describes itself as: ZettelFlow is a plugin for Obsidian that helps you to create and manage your notes in a Zettelkasten way. The licence is MIT.

When your agent uses it

  • Tasks that involve Test-driven development
  • Tasks that involve Task breakdown
  • Tasks that involve Failing and flaky tests

Example prompts

  • “break this into tasks”
  • “make the task list”
  • “/tasks”

What it can do on your machine

Read from SKILL.md and the folder at commit 0676350. 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:

    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    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

Tasks loads about 573 tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 282 words of instructions outside code blocks.

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

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 RafaelGB/Obsidian-ZettelFlow at commit 0676350, republished under its MIT licence (© RafaelGB). 282 words, ~573 tokens.

Download SKILL.mdSave it as .claude/skills/tasks/SKILL.md (or your agent's skills folder).
name
tasks
description
Stage 3 of the SDD pipeline — turn a ZettelFlow plan (in a GitHub issue comment) into an ordered TDD task checklist posted as a second issue comment. Each task has the failing test to write first and the guardrail that proves it. Use after a plan comment exists and the user says "break this into tasks", "make the task list", or "tasks for issue

/tasks — break the plan into a TDD checklist (issue comment)

Stage 3 of the SDD pipeline. Given a plan comment on a GitHub issue, post a second comment with an ordered, dependency-aware task checklist — each task is one red→green→refactor cycle and, ideally, one commit that leaves npm run verify green.

No local files — the task list lives in the GitHub issue as a comment.

Owner

Delegate to the implementation-planner agent (same agent as /plan — it already holds context from reading the issue).

Steps

The agent posts a comment containing a task checklist. For each task:

  • - [ ] **Tn**: <name> — what gets done
  • Red — the exact test file and what it asserts (cite the FR/AC it covers)
  • Green — the minimal change to pass it
  • Guardrail — always npm run verify; add npm run lint:obsidian (no new violations) for score work; es.ts/en.ts parity for i18n work
  • Commit — the Conventional Commit line

The last task is always to walk the spec's How to verify script end to end and correct it where it no longer describes what shipped. A step that turned out to be automatable becomes a test in that task, not a note for later.

Ends with a Definition of done block (all tasks checked, ACs met, the verification script walked, quality audit + reviewer clean, docs + en/es synced, issue listed in the PR's Closes set).

Right-sizing

  • A task should be completable and committable in one sitting; split if not.
  • Pure-logic units (DTOs, flow traversal, utils) get real unit tests. React components / modals / Canvas patcher are integration territory — note how each is verified rather than pretending a unit test exists.

Quality bar (the stage-3 gate)

Every task is test-first, small, and independently verifiable. Then run /implement <issue #>.

© RafaelGB, MIT. 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 .claude/skills/tasks of RafaelGB/Obsidian-ZettelFlow.

Open the folder on GitHubat commit 0676350

Compare with similar skills

Tasks 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.

Tasks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tasks this skillRafaelGB/Obsidian-ZettelFlow174—~573Automated safety check: PassMIT
CI Fix MonitorZaxbyHub/opencode-swarm490—~551Automated safety check: PassMIT
Implementericrisco/rsc-harness167—~5.9kAutomated safety check: NotesMIT
Obsidian CI Integrationjeremylongshore/tons-of-skills-marketplace2.8k—~2kAutomated safety check: PassMIT
Triage CI Flakepayloadcms/payload45k—~4.4kAutomated safety check: PassMIT
GreptimeDB Fuzz CI Failure InvestigationGreptimeTeam/greptimedb6.7k—~4.4kAutomated safety check: PassApache-2.0

Similar skills

  • CI Fix Monitor

    ZaxbyHub/opencode-swarm

    Codex adapter for monitoring and fixing CI failures on opencode-swarm PRs.

    490 GitHub stars~551 tokensUpdated today
    Testing & QAAuto-check passed
  • Implement

    ericrisco/rsc-harness

    A skill your agent uses when an approved plan and task list exist and it is time to turn them into working, tested code — the SDD phase after analyze and before verify.

    167 GitHub stars~5.9k tokensUpdated today
    Testing & QAAuto-check: notes
  • Obsidian CI Integration

    jeremylongshore/tons-of-skills-marketplace

    Set up GitHub Actions CI/CD for Obsidian plugin development.

    2.8k GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Triage CI Flake

    payloadcms/payload

    A skill your agent uses when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests

    45k GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.

    6.7k GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Fix Issue

    remix-run/remix

    Fix a reported issue in Remix from a GitHub issue. An agent skill from remix-run/remix.

    33k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed

More from RafaelGB/Obsidian-ZettelFlow

All 9 skills in this repo
  • New Action

    RafaelGB/Obsidian-ZettelFlow

    Scaffold a new ZettelFlow action following the project's 4-file convention (Action / Component / Settings / SettingsReader), register it, and document it.

    174 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Obsidian Plugin Quality

    RafaelGB/Obsidian-ZettelFlow

    Audit ZettelFlow against the official Obsidian plugin guidelines and the Community-hub automated review / quality score.

    174 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Release

    RafaelGB/Obsidian-ZettelFlow

    Cut a compliant ZettelFlow plugin release — version bump, versions.json, build, tag, and a GitHub Release whose notes follow the house format.

    174 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Specify

    RafaelGB/Obsidian-ZettelFlow

    Stage 1 of the SDD pipeline — write a ZettelFlow spec into a GitHub issue body (problem, value, functional requirements, testable acceptance criteria, capability disclosure, out-of-scope).

    174 GitHub stars~759 tokensUpdated today
    Auto-check passed
  • Sdd

    RafaelGB/Obsidian-ZettelFlow

    The Spec-Driven Development pipeline for ZettelFlow — the end-to-end flow (constitution → specify → plan → tasks → implement → verify) and which skill/agent owns each stage.

    174 GitHub stars~842 tokensUpdated today
    Auto-check passed
  • TDD

    RafaelGB/Obsidian-ZettelFlow

    The test-driven development workflow for ZettelFlow — write a failing test first, run jest, use the Obsidian mock and the bare-specifier alias mappings, and know which code is unit-testable.

    174 GitHub stars~724 tokensUpdated today
    Auto-check passed

Categories

Questions about Tasks

What does Tasks do?

Stage 3 of the SDD pipeline — turn a ZettelFlow plan (in a GitHub issue comment) into an ordered TDD task checklist posted as a second issue comment. Tasks is an agent skill from RafaelGB/Obsidian-ZettelFlow. Stage 3 of the SDD pipeline — turn a ZettelFlow plan (in a GitHub issue comment) into an ordered TDD task checklist posted as a second issue comment.

When should I use Tasks?

Tasks fits situations like: tasks that involve Test-driven development; tasks that involve Task breakdown; tasks that involve Failing and flaky tests.

How do I install Tasks in Claude Code?

Run `npx skills add RafaelGB/Obsidian-ZettelFlow --skill tasks -a claude-code`. Or copy the skill folder (.claude/skills/tasks in RafaelGB/Obsidian-ZettelFlow) into .claude/skills/tasks in your project. Claude Code loads it when a task matches its description.

How do I install Tasks in Codex?

Run `npx skills add RafaelGB/Obsidian-ZettelFlow --skill tasks -a codex`. Or copy the skill folder (.claude/skills/tasks in RafaelGB/Obsidian-ZettelFlow) into .agents/skills/tasks in your project. Codex loads it when a task matches its description.

Can I use Tasks 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 RafaelGB/Obsidian-ZettelFlow --skill tasks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tasks, .gemini/skills/tasks, .github/skills/tasks and .opencode/skills/tasks in your project.

What does Tasks need to run?

Going by SKILL.md and its folder, Tasks needs the command-line tools its instructions call (npm).

Does Tasks access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Tasks 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 Tasks use?

Tasks is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tasks use?

About 573 tokens (SKILL.md is roughly 2.3k 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 Tasks?

Skills that share tags, products or a category with Tasks: CI Fix Monitor (ZaxbyHub/opencode-swarm, 490 stars), Implement (ericrisco/rsc-harness, 167 stars), Obsidian CI Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Triage CI Flake (payloadcms/payload, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tasks?

RafaelGB (a GitHub user) maintains it in RafaelGB/Obsidian-ZettelFlow, which has 174 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.

Source: RafaelGB/Obsidian-ZettelFlow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.