agentmods.dev

musubix-sdd-workflow

musubix-sdd-workflow is a skill for Claude Code from nahisaho/katashiro. It costs 51 tokens per session (1,268 once invoked), scanned A, original, MIT.

A guide to Specification-Driven Development, a way of building software from written requirements, designs, tasks, code, and tests. It follows the MUSUBIX process and its nine project rules.

In plain words
What is it for?
Use it to define and review requirements, create designs and implementation tasks, and build features according to an existing MUSUBIX project structure.
Why use it?
It gives feature work a repeatable order and checks that requirements are clear, testable, and connected to later development work.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

not rated 0repo 9mo ago A scan 51 tokens original MIT

Good fit Use it to define and review requirements, create designs and implementation tasks, and build features according to an existing MUSUBIX project structure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nahisaho/katashiro/musubix-sdd-workflow
View source ↗ nahisaho/katashiro
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 nahisaho/katashiro --skill musubix-sdd-workflow
Clone the repo
git clone --depth 1 https://github.com/nahisaho/katashiro

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 musubix-sdd-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/nahisaho/katashiro/musubix-sdd-workflow/github.svg)](https://agentmods.dev/skills/nahisaho/katashiro/musubix-sdd-workflow)
Your own site
<a href="https://agentmods.dev/skills/nahisaho/katashiro/musubix-sdd-workflow"><img src="https://agentmods.dev/badge/skills/nahisaho/katashiro/musubix-sdd-workflow/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 musubix-sdd-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/nahisaho/katashiro/musubix-sdd-workflow"><img src="https://agentmods.dev/badge/skills/nahisaho/katashiro/musubix-sdd-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,268 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.00051 $0.01268
Opus 5.5 $0.00020 $0.00507
Sonnet 5.5 $0.00010 $0.00254
Haiku 4.5 $0.00005 $0.00127

Measured 2mo ago against content hash d22e496942eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

musubix-sdd-workflow 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/skills/musubix-sdd-workflow/SKILL.md · 211 lines

How it starts

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

MUSUBIX SDD Workflow Skill

This skill guides you through the complete SDD workflow for MUSUBIX projects.

Prerequisites

Before starting any development task:

  1. Read steering/ directory for project context
  2. Check steering/rules/constitution.md for the 9 constitutional articles
  3. Review existing specs in storage/specs/

Complete Workflow

Phase 1: Requirements Definition

Step 1: Create Requirements Document (Article IV - EARS Format)

Create requirements using EARS patterns:

# REQ-[CATEGORY]-[NUMBER]

**種別**: [UBIQUITOUS|EVENT-DRIVEN|STATE-DRIVEN|UNWANTED|OPTIONAL]
**優先度**: [P0|P1|P2]

**要件**:
[EARS形式の要件文]

**トレーサビリティ**: DES-XXX, TEST-XXX

EARS Patterns:

  • Ubiquitous: THE [system] SHALL [requirement]
  • Event-driven: WHEN [event], THE [system] SHALL [response]
  • State-driven: WHILE [state], THE [system] SHALL [response]
  • Unwanted: THE [system] SHALL NOT [behavior]
  • Optional: IF [condition], THEN THE [system] SHALL [response]
Step 2-3: Requirements Review Loop

Review requirements for:

  • EARS format compliance
  • Completeness and clarity
  • Testability
  • Traceability readiness

Repeat until no issues remain.

Phase 2: Design

Step 4: Create Design Document (Article VII - Design Patterns)

Create C4 model design documents:

  1. Context Level: System boundaries and external actors
  2. Container Level: Technology choices and container composition
  3. Component Level: Internal structure of containers
  4. Code Level: Implementation details

Design document template:

# DES-[CATEGORY]-[NUMBER]

## トレーサビリティ
- 要件: REQ-XXX

## C4モデル
### Level 2: Container
[PlantUML diagram]

## コンポーネント設計
[Component details]
Step 5-6: Design Review Loop

Review design for:

  • Requirement coverage
  • SOLID principles compliance
  • Design pattern appropriateness
  • Traceability to requirements

Repeat until no issues remain.

Phase 3: Task Decomposition

Step 7: Generate Tasks

Read the full file on GitHub · 211 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 · 211 lines · 51 tokens per session scan A d22e496942eb

Subscribe to this mod's changes

musubix-sdd-workflow is a skill published in the GitHub repository nahisaho/katashiro (0 stars, last pushed 9mo ago), licensed MIT. It adds 51 tokens to every session and 1,268 once invoked, about $0.0002 per session on Opus 5.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-31.

PlanningWriting and docs
Related

musubix-sdd-workflow compared with skills from other repositories

musubix-sdd-workflow next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
musubix-sdd-workflownahisaho/katashiroSkill09mo agoMITA51Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code