Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

spdd-story

Étoiles4

Forks0

Mis à jour26 mai 2026 à 20:50

Use when a large SPDD requirement needs to be split into independent, deliverable user stories before analysis and REASONS Canvas work.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

danmestas

danmestas/wardrobe

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

name	spdd-story
version	0.1.0
targets	["claude-code","codex","gemini","pi"]
type	skill
description	Use when a large SPDD requirement needs to be split into independent, deliverable user stories before analysis and REASONS Canvas work.
category	{"primary":"workflow"}

SPDD Story

Break large requirements into independent, deliverable stories before deeper analysis.

Announce at start: "I'm using the spdd-story skill to split the requirement into SPDD-ready stories."

When to use

Use this when the input bundles multiple outcomes, personas, bounded contexts, delivery milestones, or acceptance surfaces. Skip it when the user already supplied a small, coherent story.

Story rules

Each story must be:

Independent: can ship without relying on another unfinished story.
Negotiable: captures outcome, not implementation commands.
Valuable: has visible user/business value.
Estimable: bounded enough for a single implementation plan.
Small: one coherent behavior slice.
Testable: acceptance criteria are observable.

Output format

For each story:

## Story N: <title>

### Background
<why this matters>

### Business value
<what improves when this ships>

### Scope in
- ...

### Scope out
- ...

### Acceptance criteria
- Given ..., when ..., then ...

Handoff

After splitting, run spdd-alignment on the selected story before spdd-analysis. Do not generate architecture or code from the raw split output.

Plus depuis ce dépôt

même dépôt

helland

danmestas/wardrobe

The Pat Helland lens: treat durable data as immutable, append-only facts that carry their own identity and version; and design across service, machine, or org boundaries assuming you cannot have distributed transactions — only idempotent, at-least-once messages that must be reconciled. Apply this on in-place updates and overwrites, "just UPDATE the row," two-phase commit or distributed transactions at scale, exactly-once delivery assumptions, shared mutable state across services, and any data that crosses a boundary of service, machine, org, or time. Trigger even when Helland isn't named — the smell is mutation-in-place and pretending distributed systems can be transactional.

2026-07-184

hickey

danmestas/wardrobe

The Rich Hickey lens: pursue simple (un-braided, one role) over easy (familiar, near-at-hand), decomplect concerns that got tangled together, and separate value, identity, state, and time. Apply this whenever "easy," "convenient," or "it's what we already use" is doing the work of justifying a design; when state is braided into logic, policy into mechanism, or data into behavior; when object-soup would be plainer as data; and when a hard design decision is being made at the keyboard under time pressure instead of thought through first. Trigger even when Hickey isn't named — the smell is complecting, and confusing "easy" with "simple."

2026-07-184

carmack

danmestas/wardrobe

The John Carmack lens: minimize the mutable state you have to reason about, do the simple thing before the clever one, and treat correctness tooling — static analysis, warnings-as-errors, determinism — as non-negotiable. Apply this on sprawling mutable state, "we'll clean it up later," debugging by print- statement whack-a-mole, silenced compiler warnings, nondeterministic or non-reproducible behavior, premature abstraction, perf work that skips measurement, and any "what should we actually work on" prioritization call. Trigger even when Carmack isn't named — the smell is code whose full set of states you can't hold in your head, and effort that isn't ruthlessly focused.

2026-07-184

bellard

danmestas/wardrobe

The Fabrice Bellard lens: build the smallest self-contained thing that fully does the job, get performance from insight instead of hardware, and reuse existing machinery instead of reinventing it. Apply this whenever code is growing dependencies, frameworks, services, or infrastructure to solve a problem that a smaller, sharper implementation could handle — or whenever someone says a thing needs a cluster, a big framework, or a rewrite. Use for size/complexity audits, "do we really need this dependency/service?" questions, performance work where the reflex is to add hardware or caching, green-field "should this be one file or a platform?" decisions, and any moment the answer is trending toward "that's impractical, you'd need X." Trigger even when the user doesn't name Bellard — the smell is scope inflation and reaching for resources over insight.

2026-07-184

vault-autoresearch

danmestas/wardrobe

Use when iteratively researching a topic and filing the synthesis into an Obsidian vault for later ingestion. Output goes to `<vault>/raw/` (NOT directly into wiki pages) so that `vault-ingest` can process it on its own schedule. Triggers: '/vault-autoresearch', 'autoresearch [topic]', 'research [topic] into the vault', 'deep dive into [topic]', 'find everything about [topic] for the vault', 'research and stage'.

2026-07-144

vault-ingest

danmestas/wardrobe

Ingest sources into the Obsidian wiki vault. Reads a source, extracts entities and concepts, creates or updates wiki pages, cross-references, and logs the operation. Supports files, URLs, and batch mode. Triggers on: ingest, process this source, add this to the wiki, read and file this, batch ingest, ingest all of these, ingest this url.

2026-07-144

name	spdd-story
version	0.1.0
targets	["claude-code","codex","gemini","pi"]
type	skill
description	Use when a large SPDD requirement needs to be split into independent, deliverable user stories before analysis and REASONS Canvas work.
category	{"primary":"workflow"}

SPDD Story

Break large requirements into independent, deliverable stories before deeper analysis.

Announce at start: "I'm using the spdd-story skill to split the requirement into SPDD-ready stories."

When to use

Use this when the input bundles multiple outcomes, personas, bounded contexts, delivery milestones, or acceptance surfaces. Skip it when the user already supplied a small, coherent story.

Story rules

Each story must be:

Independent: can ship without relying on another unfinished story.
Negotiable: captures outcome, not implementation commands.
Valuable: has visible user/business value.
Estimable: bounded enough for a single implementation plan.
Small: one coherent behavior slice.
Testable: acceptance criteria are observable.

Output format

For each story:

## Story N: <title>

### Background
<why this matters>

### Business value
<what improves when this ships>

### Scope in
- ...

### Scope out
- ...

### Acceptance criteria
- Given ..., when ..., then ...

Handoff

After splitting, run spdd-alignment on the selected story before spdd-analysis. Do not generate architecture or code from the raw split output.