CodeGraphMCPServer: Command for Claude Code

.claude/commands/sdd-tasks.md

sdd-tasks is a command for Claude Code from nahisaho/CodeGraphMCPServer. It costs 0 tokens per session (3,589 once invoked), scanned A, original, MIT.

A command that turns a software design into a list of implementation tasks. It also links those tasks to the project's requirements so the work can be checked against them.

In plain words
What is it for?
Use it to plan features such as authentication, payment processing, or a user dashboard after creating their design and requirements files.
Why use it?
It breaks a large feature into actionable work and prevents task planning when the required design or requirements documents are missing.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the AskUserQuestion tool.

This is nahisaho/CodeGraphMCPServer's own configuration. It tells Claude Code how to work on CodeGraphMCPServer itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything CodeGraphMCPServer configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nahisaho/CodeGraphMCPServer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nahisaho/CodeGraphMCPServer/main/.claude/commands/sdd-tasks.md
Clone the repo
git clone --depth 1 https://github.com/nahisaho/CodeGraphMCPServer

Made for: Claude Code.

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/commands/nahisaho/codegraphmcpserver/sdd-tasks/github.svg)](https://agentmods.dev/commands/nahisaho/codegraphmcpserver/sdd-tasks)
Your own site
<a href="https://agentmods.dev/commands/nahisaho/codegraphmcpserver/sdd-tasks"><img src="https://agentmods.dev/badge/commands/nahisaho/codegraphmcpserver/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/commands/nahisaho/codegraphmcpserver/sdd-tasks"><img src="https://agentmods.dev/badge/commands/nahisaho/codegraphmcpserver/sdd-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,589 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.00000 $0.03589
Opus 5.5 $0.00000 $0.01436
Sonnet 5.5 $0.00000 $0.00718
Haiku 4.5 $0.00000 $0.00359

Measured 2mo ago against content hash 0c3522fb17df, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

.claude/commands/sdd-tasks.md · 618 lines

How it starts

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

SDD Tasks Command

Break down design into actionable implementation tasks.


Instructions for Claude

You are executing the /sdd-tasks [feature-name] command to create a task breakdown document.

Command Format

/sdd-tasks authentication
/sdd-tasks payment-processing
/sdd-tasks user-dashboard

Your Task

Generate a comprehensive task breakdown that transforms the design into actionable implementation tasks with full requirements traceability.


Process

1. Read Context

CRITICAL: Read these files first:

# Design and Requirements
storage/specs/{{feature-name}}-design.md
storage/specs/{{feature-name}}-requirements.md

# Steering Context
steering/structure.md
steering/tech.md
steering/product.md

2. Verify Prerequisites

Check design file exists:

❌ **Error**: Design document not found

Expected: storage/specs/{{feature-name}}-design.md

Please run `/sdd-design {{feature-name}}` first.

Tasks cannot be created without design (Article V: Traceability).

Check requirements file exists:

❌ **Error**: Requirements document not found

Expected: storage/specs/{{feature-name}}-requirements.md

Task breakdown requires requirements for traceability.

3. Generate Task Breakdown

Use template from templates/tasks.md.

Task Structure

Each task follows this format:

### TASK-XXX: [Task Title]

**Priority**: P0/P1/P2/P3
**Story Points**: [1/2/3/5/8/13]
**Estimated Hours**: [N]
**Assignee**: [Unassigned initially]
**Status**: Not Started

**Description**:
[Clear description of what needs to be done]

**Requirements Coverage**:

- REQ-XXX-NNN: [Requirement title]
- REQ-XXX-NNN: [Requirement title]

**Acceptance Criteria**:

- [ ] [Testable criterion 1]
- [ ] [Testable criterion 2]
- [ ] [Testable criterion 3]

**Dependencies**:

- TASK-XXX: [Dependency description]

**Test-First Checklist** (Article III):

- [ ] Tests written BEFORE implementation
- [ ] Red: Failing test committed
- [ ] Green: Minimal implementation passes test
- [ ] Blue: Refactored with confidence

**Implementation Notes**:
[File paths, code snippets, technical details]

**Validation**:

```bash

Read the full file on GitHub · 618 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. 2mo ago First seen · 618 lines · 0 tokens per session scan A 0c3522fb17df

Subscribe to this mod's changes

sdd-tasks is a command published in the GitHub repository nahisaho/CodeGraphMCPServer (14 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,589 tokens. 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

sdd-tasks compared with commands from other repositories

sdd-tasks next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
sdd-tasksnahisaho/CodeGraphMCPServerCommand1411mo agoMITA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code