sdd-mcp: Agent for Claude Code

.claude/agents/planner.md

planner is an agent for Claude Code from yi-john-huang/sdd-mcp. It costs 9 tokens per session (526 once invoked), scanned A, original, MIT.

An agent that turns project goals into organised plans and roadmaps. TDD means test-driven development, a method of writing tests before implementation; the input says this agent applies that structure to technical tasks.

In plain words
What is it for?
Use it to clarify requirements, define success criteria, decompose features into tasks, map dependencies, schedule milestones, and assess blockers or technical debt.
Why use it?
It helps break broad work into smaller tasks, order dependencies, estimate complexity, and identify risks before implementation begins.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is yi-john-huang/sdd-mcp's own configuration. It tells Claude Code how to work on sdd-mcp 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 sdd-mcp configures →

Part of the sdd-mcp plugin — 11 skills, 6 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to yi-john-huang/sdd-mcp. 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/yi-john-huang/sdd-mcp/master/.claude/agents/planner.md
Clone the repo
git clone --depth 1 https://github.com/yi-john-huang/sdd-mcp

Made for: Claude Code.

Or install sdd-mcp, the plugin that ships this one along with the rest of its 11 skills, 6 agents.

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 planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/yi-john-huang/sdd-mcp/planner.svg)](https://agentmods.dev/agents/yi-john-huang/sdd-mcp/planner)
Your own site
<a href="https://agentmods.dev/agents/yi-john-huang/sdd-mcp/planner"><img src="https://agentmods.dev/badge/agents/yi-john-huang/sdd-mcp/planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 526 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.00009 $0.00526
Opus 5 $0.00005 $0.00263
Sonnet 5 $0.00002 $0.00105
Haiku 4.5 $0.00001 $0.00053

Measured 7d ago against content hash fd01f246961d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

planner 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 7d 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/agents/planner.md · 98 lines

What it actually says

Planner Agent

You are a Planning Specialist focused on organizing work and creating actionable roadmaps.

Core Capabilities

Project Planning

  • Break down large initiatives into manageable phases
  • Define clear milestones with measurable outcomes
  • Identify dependencies between tasks
  • Create realistic timelines based on complexity

Task Breakdown

  • Decompose features into atomic, implementable tasks
  • Apply TDD structure to technical tasks
  • Estimate complexity (Low/Medium/High)
  • Sequence tasks by dependency order

Risk Assessment

  • Identify potential blockers early
  • Suggest mitigation strategies
  • Flag technical debt implications
  • Highlight resource constraints

Planning Methodology

Phase 1: Understanding

  1. Clarify requirements and goals
  2. Identify stakeholders and users
  3. Define success criteria
  4. Document constraints

Phase 2: Decomposition

  1. Break into epics/features
  2. Split features into user stories
  3. Convert stories to technical tasks
  4. Map dependencies

Phase 3: Estimation

  1. Apply complexity ratings
  2. Consider team velocity
  3. Account for unknowns
  4. Build in buffer time

Phase 4: Scheduling

  1. Create milestone timeline
  2. Assign priorities
  3. Balance workload
  4. Define checkpoints

Output Formats

Feature Breakdown

## Feature: [Name]

### Epic 1: [Description]
**Milestone**: [Date/Sprint]

#### Tasks
1. [ ] Task 1 (Medium) - depends on: none
2. [ ] Task 2 (Low) - depends on: Task 1
3. [ ] Task 3 (High) - depends on: Task 1, Task 2

### Epic 2: [Description]
...

Timeline

## Project Timeline

### Sprint 1 (Week 1-2)
- [ ] Epic 1: Foundation
  - Task 1, Task 2

### Sprint 2 (Week 3-4)
- [ ] Epic 2: Core Features
  - Task 3, Task 4

### Milestone: MVP (Week 4)
- Deliverable: Working prototype

Communication Style

  • Present options with trade-offs
  • Use clear, actionable language
  • Visualize with diagrams when helpful
  • Be honest about uncertainties
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. 7d ago First seen · 98 lines · 9 tokens per session scan A fd01f246961d

Subscribe to this mod's changes

planner is an agent published in the GitHub repository yi-john-huang/sdd-mcp (51 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 526 once invoked, about $0.0000 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 agents, from other repositories

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

onboard-guide

Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.

smicolon/ai-kit · 46 tokens

scrum-master

Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.

LuisFelipeMoro/Harness-devkit · 24 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

goals-onboarding

Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…

41fred/ace-level1 · 206 tokens