Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria.
Install Sdd Work Decomposition
$ npx skills add magnus919/hermes-profiles --skill sdd-work-decomposition -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/hermes-profiles sdd-work-decomposition --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sdd-work-decomposition .claude/skills/sdd-work-decomposition && rm -rf skills-srcUse ~/.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/
Install the "sdd-work-decomposition" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-work-decomposition into .claude/skills/sdd-work-decomposition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-work-decomposition", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-work-decompositionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add magnus919/hermes-profiles --skill sdd-work-decomposition -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/hermes-profiles sdd-work-decomposition --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sdd-work-decomposition .agents/skills/sdd-work-decomposition && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sdd-work-decomposition" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-work-decomposition into .agents/skills/sdd-work-decomposition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-work-decomposition", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/hermes-profiles --skill sdd-work-decomposition -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/hermes-profiles sdd-work-decomposition --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sdd-work-decomposition .cursor/skills/sdd-work-decomposition && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sdd-work-decomposition" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-work-decomposition into .cursor/skills/sdd-work-decomposition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-work-decomposition", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/magnus919/hermes-profiles.git --path skills/sdd-work-decomposition--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add magnus919/hermes-profiles --skill sdd-work-decomposition -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/hermes-profiles sdd-work-decomposition --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sdd-work-decomposition .gemini/skills/sdd-work-decomposition && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sdd-work-decomposition" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-work-decomposition into .gemini/skills/sdd-work-decomposition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-work-decomposition", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install magnus919/hermes-profiles sdd-work-decompositionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add magnus919/hermes-profiles --skill sdd-work-decomposition -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sdd-work-decomposition .github/skills/sdd-work-decomposition && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sdd-work-decomposition" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-work-decomposition into .github/skills/sdd-work-decomposition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-work-decomposition", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/hermes-profiles --skill sdd-work-decomposition -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install magnus919/hermes-profiles sdd-work-decomposition --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sdd-work-decomposition .opencode/skills/sdd-work-decomposition && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sdd-work-decomposition" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-work-decomposition into .opencode/skills/sdd-work-decomposition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-work-decomposition", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sdd-work-decomposition- GitHub stars
- 282
- Token cost
- ~1.4k tokens
- SKILL.md length
- 637 words
- Files
- 6 (incl. scripts, references)
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- MIT
At a glance
SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria.
- A reviewed specification needs to be broken into implementable tasks
- SKILL.md covers SDD Pipeline Position, Core Principle: Spec Is the Plan, Artifact-Pyramid Output:… and Loading Guidance, plus 2 more sections
- Runs Shell scripts from its folder
- Tasks that involve User stories
What it does
Sdd Work Decomposition is an agent skill from magnus919/hermes-profiles. SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria. Owns the mapping from specification to executable work units, producing artifact-pyramid-compliant TASK-PLAN.md outputs. Trigger when a reviewed specification needs to be broken into implementable tasks.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/claude-dot-md-as-spec-layer.md`, `references/dependency-mapping.md` and `references/task-decomposition-methodology.md`).
It sits in Product & Project Management, covering User stories. The repository describes itself as: Curated Hermes Agent profiles for specialist swarms — opinionated, Hermes-optimized, artifact-pyramid native. The licence is MIT.
When your agent uses it
- A reviewed specification needs to be broken into implementable tasks
- Tasks that involve User stories
Example prompts
- “/sdd-work-decomposition”
Requirements
- A Bash shell
What it can do on your machine
Read from SKILL.md and the folder at commit 867a555. 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
Ships 1 file in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Sdd Work Decomposition loads about 1.4k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 637 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from magnus919/hermes-profiles at commit 867a555, republished under its MIT licence (© magnus919). 637 words, ~1,384 tokens.
Download SKILL.mdSave it as
.claude/skills/sdd-work-decomposition/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- sdd-work-decomposition
- description
- SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria. Owns the mapping from specification to executable work units, producing artifact-pyramid-compliant TASK-PLAN.md outputs. Trigger when a reviewed specification needs to be broken into implementable tasks.
- version
- 1.0.0
- author
- Hermes Agent community
- license
- MIT
SDD Work Decomposition
Translating a reviewed, approved specification into an executable sequence of tasks with explicit dependencies, per-task acceptance criteria, and integration directives for the implementation agent.
SDD Pipeline Position
SPECIFY → [PLAN] → TASKS → IMPLEMENT → VERIFY
↑
You are hereThis skill bridges the gap between what to build (the spec) and how to build it in independent, verifiable units. It produces both the human-readable task plan and the CLAUDE.md / AGENTS.md content that drives the implementation agent.
Core Principle: Spec Is the Plan
This skill does not invent a plan from scratch. It extracts the plan from the specification. The spec already defines the behavior the system must exhibit — each behavior maps to a task. Every task traces to a specific section of SPEC.md. There is no work in the plan that is not required by the spec, and no requirement in the spec that is not addressed by at least one task.
This is what distinguishes SDD decomposition from general-purpose project planning. The planner does not ask "what work needs to happen?" — the spec already answered that. The planner asks "how do we sequence and package this work for safe execution?"
Artifact-Pyramid Output: TASK-PLAN.md
The task plan follows the artifact-pyramid structure:
| Layer | Content | File |
|---|---|---|
| L1 | Phase overview — total task count, critical path estimate, key dependencies, recommended execution order | 00-index.md (entry point) |
| L2 | Task groups by phase or feature area — dependency graph, per-group acceptance criteria derived from spec sections | Individual *.phase.md files |
| L3 | Individual task cards — each with spec-derived ACs, estimated complexity, preconditions, CLAUDE.md directives | tasks/ directory |
| SOURCES | Cross-reference from each task to the SPEC.md section it implements | Footer of each file |
Loading Guidance
| Reference | When to load | File |
|---|---|---|
| Task Decomposition Methodology | Before writing any task plan — patterns for spec-to-task extraction, sizing, atomicity | references/task-decomposition-methodology.md |
| Dependency Mapping | Sequencing tasks with real constraints — spec-derived dependency chains, not guesswork | references/dependency-mapping.md |
| CLAUDE.md as Spec Layer | After producing the task plan — generating CLAUDE.md directives for the implementation agent | references/claude-dot-md-as-spec-layer.md |
| Template | When to use | File |
|---|---|---|
| TASK-PLAN.md | Producing the full task plan from a reviewed specification | templates/TASK-PLAN.md |
| Script | When to run | File |
|---|---|---|
spec-to-tasks.sh | After authoring a TASK-PLAN.md — validates every spec requirement has a covering task | scripts/spec-to-tasks.sh |
Trigger Conditions
Invoke this skill when:
- A reviewed, approved specification needs to be broken into executable tasks
- An existing task plan needs restructuring because discovered dependencies invalidated the original sequencing
- Multiple specifications exist for a coordinated release and need cross-spec dependency resolution
- An implementation agent needs a CLAUDE.md or AGENTS.md generated from the spec and task plan
Show full SKILL.md (231 more words)Show less
Decomposition Rules
Atomicity
Each task must be independently implementable and verifiable. The test: if a task is completed but its acceptance criteria can't be checked until another task also completes, the tasks are not atomic — merge them or redefine their boundaries.
Spec Traceability
Every task body MUST include a Spec: -- section X reference back to the SPEC.md section that defines its requirements. This is not optional metadata — it is the mechanism that prevents scope drift during implementation.
Task Size
No task should exceed one session of implementation work (typically 30-120 minutes for an AI coding agent, depending on complexity). Tasks larger than this signal that the spec section is too coarse and needs refinement. Decompose the spec section further before decomposing the task.
Dependency Honesty
Record only real, spec-derived dependencies. A dependency is real when: task B requires task A's output (a function signature, a data structure, a schema, a module interface) that B cannot stub or mock. Dependencies that can be satisfied by a contract or interface definition are NOT real dependencies — define the contract in the spec instead.
The CLAUDE.md Handoff
After the task plan is complete, this skill generates the CLAUDE.md directives that the implementation agent reads. These directives include:
- Which SPEC.md sections and task plan files to load
- The execution order and dependency constraints
- The acceptance criteria format expected by verification
- The escalation protocol for spec ambiguities
© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (scripts, references) in skills/sdd-work-decomposition of magnus919/hermes-profiles.
- SKILL.md
- references/claude-dot-md-as-spec-layer.md
- references/dependency-mapping.md
- references/task-decomposition-methodology.md
- scripts/spec-to-tasks.sh
- templates/TASK-PLAN.md
Open the folder on GitHubat commit 867a555
Compare with similar skills
Sdd Work Decomposition 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sdd Work Decomposition this skillmagnus919/hermes-profiles | 282 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Project Planneradrianpuiu/claude-skills-marketplace | 100 | 1 repos | ~6k | Automated safety check: Pass | None | |
| Feature ForgeJeffallan/claude-skills | 12k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Refactor Design Reportpenwyp/ClaudePreference | 136 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Spec WorkflowTencentCloudBase/CloudBase-AI-Toolkit | 1.1k | 2 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Cas Supervisor Checklistcodingagentsystem/cas | 176 | — | ~349 | Automated safety check: Pass | MIT |
Similar skills
Feature Forge
Jeffallan/claude-skills
Runs a structured requirements interview to produce a feature specification with EARS requirements, acceptance criteria and an implementation checklist.
Refactor Design Report
penwyp/ClaudePreference
Produce a professional, code-grounded refactor or implementation design report from identified technical problems, product gaps, review findings, architecture concerns, or frontend-backend contract…
Spec Workflow
TencentCloudBase/CloudBase-AI-Toolkit
A skill your agent uses when medium-to-large changes need explicit requirements, technical design, and task planning before implementation, especially for multi-module work, unclear acceptance…
Cas Supervisor Checklist
codingagentsystem/cas
Quick startup checklist for factory supervisors. An agent skill from codingagentsystem/cas.
Spec Driven Loop
sickn33/agentic-awesome-skills
Freeze PRD, technical design, and acceptance criteria before medium-to-large Codex work; coordinate agents with explicit ownership, then judge delivery from diffs, tests, and evidence.
More from magnus919/hermes-profiles
All 31 skills in this repoData Scientist
magnus919/hermes-profiles
PhD-level expertise in data science, statistics, and machine learning.
Brand Designer
magnus919/hermes-profiles
Create comprehensive brand identity documentation for any brand.
Sdd Authoring
magnus919/hermes-profiles
Specification authoring for AI-native SDD — writes formal specifications in structured formats (Gherkin, user stories, acceptance criteria), enforces spec quality gates, and produces…
Sdd Verification
magnus919/hermes-profiles
SDD acceptance criteria verification — maps specification acceptance criteria to tests, validates implementation output against spec requirements, and produces artifact-pyramid-compliant…
Artifact Pyramids
magnus919/hermes-profiles
Progressive disclosure for what AI agents produce. An agent skill from magnus919/hermes-profiles.
SEO Audit
magnus919/hermes-profiles
Full-spectrum SEO + AEO audit skill — technical crawl analysis, on-page content optimization, structured data (JSON-LD/Schema.org) validation, Ghost CMS metadata completion, answer engine…
Related
Questions about Sdd Work Decomposition
What does Sdd Work Decomposition do?
SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria. Sdd Work Decomposition is an agent skill from magnus919/hermes-profiles. SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria.
When should I use Sdd Work Decomposition?
Sdd Work Decomposition fits situations like: A reviewed specification needs to be broken into implementable tasks; tasks that involve User stories.
How do I install Sdd Work Decomposition in Claude Code?
Run `npx skills add magnus919/hermes-profiles --skill sdd-work-decomposition -a claude-code`. Or copy the skill folder (skills/sdd-work-decomposition in magnus919/hermes-profiles) into .claude/skills/sdd-work-decomposition in your project. Claude Code loads it when a task matches its description.
How do I install Sdd Work Decomposition in Codex?
Run `npx skills add magnus919/hermes-profiles --skill sdd-work-decomposition -a codex`. Or copy the skill folder (skills/sdd-work-decomposition in magnus919/hermes-profiles) into .agents/skills/sdd-work-decomposition in your project. Codex loads it when a task matches its description.
Can I use Sdd Work Decomposition 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 magnus919/hermes-profiles --skill sdd-work-decomposition -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sdd-work-decomposition, .gemini/skills/sdd-work-decomposition, .github/skills/sdd-work-decomposition and .opencode/skills/sdd-work-decomposition in your project.
What does Sdd Work Decomposition need to run?
Going by SKILL.md and its folder, Sdd Work Decomposition needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
Does Sdd Work Decomposition access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Sdd Work Decomposition 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Sdd Work Decomposition use?
Sdd Work Decomposition is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sdd Work Decomposition use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.
What are the alternatives to Sdd Work Decomposition?
Skills that share tags, products or a category with Sdd Work Decomposition: Project Planner (adrianpuiu/claude-skills-marketplace, 100 stars), Feature Forge (Jeffallan/claude-skills, 12k stars), Refactor Design Report (penwyp/ClaudePreference, 136 stars) and Spec Workflow (TencentCloudBase/CloudBase-AI-Toolkit, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sdd Work Decomposition?
magnus919 (a GitHub user) maintains it in magnus919/hermes-profiles, which has 282 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on June 27, 2026.
Source: magnus919/hermes-profiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.