sdd-tasks

sdd-tasks is a skill for Claude Code, Codex from felipefontoura/pi-sdd-kit. It costs 62 tokens per session (1,489 once invoked), scanned A, original, MIT.

A workflow for turning an approved software design into a practical task plan. SDD means software design document, and the plan includes dependencies, acceptance checks, file targets, and verification steps.

In plain words
What is it for?
Use it to create or update implementation tasks after a design has been approved, including what to build first and how to confirm each task works.
Why use it?
It breaks a large approved design into smaller pieces that developers can implement and check in order.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create or update implementation tasks after a design has been approved, including what to build first and how to confirm each task works.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/felipefontoura/pi-sdd-kit/sdd-tasks
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add felipefontoura/pi-sdd-kit --skill sdd-tasks
Clone the repo
git clone --depth 1 https://github.com/felipefontoura/pi-sdd-kit

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sdd-tasks

README.md
[![agentmods](https://agentmods.dev/badge/skills/felipefontoura/pi-sdd-kit/sdd-tasks/github.svg)](https://agentmods.dev/skills/felipefontoura/pi-sdd-kit/sdd-tasks)
Your own site
<a href="https://agentmods.dev/skills/felipefontoura/pi-sdd-kit/sdd-tasks"><img src="https://agentmods.dev/badge/skills/felipefontoura/pi-sdd-kit/sdd-tasks/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sdd-tasks

Your own site · 80×15
<a href="https://agentmods.dev/skills/felipefontoura/pi-sdd-kit/sdd-tasks"><img src="https://agentmods.dev/badge/skills/felipefontoura/pi-sdd-kit/sdd-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,489 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.01489
Opus 5 $0.00031 $0.00745
Sonnet 5 $0.00012 $0.00298
Haiku 4.5 $0.00006 $0.00149

Measured 9d ago against content hash 5d86bf3877cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

sdd-tasks scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/sdd-tasks/SKILL.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SDD Tasks

Convert an approved design into an implementation task plan.

Purpose

Tasks define how much work exists and in what order it should be done. They must be small, independently implementable, dependency-aware, and verifiable.

Workflow

  1. Load the SDD reference.

    • Read ../_shared/references/sdd-practical.md.
    • Apply the Language Policy: respond and write artifacts in the user's initial chat language while keeping skill instructions and templates in EN-US.
    • Read ../_shared/references/templates.md when drafting the artifact.
    • Use package-level templates/tasks.md as the user-facing template when available.
    • Use the SDD Handoff Template and package-level templates/handoff.md when creating or refreshing .ai/sdd/handoff/sdd-brief.md.
    • Load relevant .ai/steering/*.md files when present, especially product.md, tech-stack.md, conventions.md, and principles.md.
  2. Locate the feature and validate the gate.

    • Use .ai/sdd/specs/NNN-feature-name/.
    • Read .status.
    • Validate .status against the official status values from sdd-practical.md.
    • If .status is missing or invalid, stop and ask the user to repair it; do not infer design approval from design.md existing.
    • Block if status is not design:approved, unless the user explicitly asks for draft planning.
    • If blocked, report the current status and recommend /skill:sdd-spec approval as the next safe action.
    • Read requirements.md and design.md completely.
    • Read decisions.md if it exists.
  3. Explore implementation context.

    • Inspect relevant files, tests, package scripts, project conventions, and existing patterns.
    • Identify likely files to create or modify.
    • Identify verification commands from package.json, Makefile, README, CI config, or project docs.
  4. Decompose work.

    • Create tasks that are independently implementable after dependencies are complete.
    • Avoid circular dependencies.
    • Keep small-project tasks around 30 minutes to 2 hours.
    • Keep medium-project tasks around 1 to 4 hours.
    • Merge tasks that cannot be verified independently.
    • Include tests and verification inside each task; do not create a separate testing-only task unless explicitly needed.
    • Prefer implementation slices that deliver visible value when the requirements contain user stories.
    • For small projects, keep slices lightweight and optional; do not add ceremony when a flat task list is clearer.

Read the full file on GitHub · 114 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 114 lines · 62 tokens per session scan A 5d86bf3877cf

Subscribe to this mod's changes

sdd-tasks is a skill published in the GitHub repository felipefontoura/pi-sdd-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,489 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

surf

Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.

w-winter/dot314 · 60 tokens

prose-review

Review prose written for others (e.g., user-facing documentation, prompts for other LLMs, reports, plans, inline comments, docstrings) for local jargon leakage, orphaned references, missing grounding, and audience or genre mismatch. Always run on prose you produce or materially edit, except for routine conversational…

w-winter/dot314 · 84 tokens

text-search

Search indexed text corpora with qmd. For indexed content, prefer qmd over grep.

w-winter/dot314 · 22 tokens

repoprompt-tool-guidance-refresh

Refresh RepoPrompt tool guidance when the CLI/MCP surface changes. Tracks RepoPrompt CE (rpce-cli, the maintained target) across versions, and can diff the frozen Classic CLI (rp-cli) against CE. Uses /.pi/agent/skills/repoprompt-tool-guidance-refresh/scripts/track-rp-version.sh to capture/diff --help and -l (tool…

w-winter/dot314 · 115 tokens

xcodebuildmcp

Build/test Xcode projects via the XcodeBuildMCP MCP server using a local CLI wrapper for pi (no MCP support). Use when the user mentions Xcode, xcodebuild, iOS builds/tests, or XcodeBuildMCP.

w-winter/dot314 · 56 tokens

open-pencil

Work with Figma .fig design files and the running OpenPencil editor — inspect structure, query nodes, analyze design tokens, export PNG/SVG/PDF/JSX, and modify designs programmatically. Use when asked to open, inspect, export, analyze, or edit .fig files, or to control the running OpenPencil app.

open-pencil/skills · 73 tokens