Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Specification authoring for AI-native SDD — writes formal specifications in structured formats (Gherkin, user stories, acceptance criteria), enforces spec quality gates, and produces…
Install Sdd Authoring
$ npx skills add magnus919/hermes-profiles --skill sdd-authoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/hermes-profiles sdd-authoring --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-authoring .claude/skills/sdd-authoring && 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-authoring" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-authoring into .claude/skills/sdd-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-authoring", 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-authoringType 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-authoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/hermes-profiles sdd-authoring --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-authoring .agents/skills/sdd-authoring && 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-authoring" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-authoring into .agents/skills/sdd-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-authoring", 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-authoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/hermes-profiles sdd-authoring --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-authoring .cursor/skills/sdd-authoring && 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-authoring" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-authoring into .cursor/skills/sdd-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-authoring", 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-authoring--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-authoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/hermes-profiles sdd-authoring --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-authoring .gemini/skills/sdd-authoring && 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-authoring" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-authoring into .gemini/skills/sdd-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-authoring", 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-authoringInstalls 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-authoring -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-authoring .github/skills/sdd-authoring && 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-authoring" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-authoring into .github/skills/sdd-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-authoring", 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-authoring -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-authoring --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-authoring .opencode/skills/sdd-authoring && 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-authoring" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-authoring into .opencode/skills/sdd-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-authoring", 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-authoring- GitHub stars
- 289
- Token cost
- ~1.4k tokens
- SKILL.md length
- 632 words
- Files
- 6 (incl. scripts, references)
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- MIT
At a glance
Specification authoring for AI-native SDD — writes formal specifications in structured formats (Gherkin, user stories, acceptance criteria), enforces spec quality gates, and produces…
- Works in 7 steps: Problem statement — what problem this… → Scope boundary — explicit in-scope and… → User stories — prioritized, with links… → …
- Requirements documents need to be authored from scratch
- SKILL.md covers SDD Pipeline Position, Artifact-Pyramid Output: SPEC.md, Loading Guidance and Trigger Conditions, plus 3 more sections
- Runs Shell scripts from its folder
What it does
Sdd Authoring is an agent skill from 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 artifact-pyramid-compliant SPEC.md outputs. Trigger when specifications or requirements documents need to be authored from scratch or refined.
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/acceptance-criteria-design.md`, `references/gherkin-patterns.md` and `references/spec-quality-gates.md`).
It sits in Product & Project Management, covering User stories, Quality gates and PRD writing. 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
- Requirements documents need to be authored from scratch
- Tasks that involve User stories
- Tasks that involve Quality gates
Example prompts
- “/sdd-authoring”
Requirements
- A Bash shell
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Problem statement — what problem this solves and why it matters
- Scope boundary — explicit in-scope and out-of-scope
- User stories — prioritized, with links to acceptance criteria
- Acceptance criteria — per-story, framed as Given/When/Then or bulleted pass/fail conditions
- Edge cases — explicit enumeration of boundary conditions, error states, invalid inputs
- Non-functional requirements — performance, security, observability, compliance, accessibility
- Data contracts / interfaces — schemas, APIs, events (can be stubs that get refined in later phases)
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 Authoring loads about 1.4k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 632 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). 632 words, ~1,449 tokens.
Download SKILL.mdSave it as
.claude/skills/sdd-authoring/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- sdd-authoring
- description
- Specification authoring for AI-native SDD — writes formal specifications in structured formats (Gherkin, user stories, acceptance criteria), enforces spec quality gates, and produces artifact-pyramid-compliant SPEC.md outputs. Trigger when specifications or requirements documents need to be authored from scratch or refined.
- version
- 1.0.0
- author
- Hermes Agent community
- license
- MIT
SDD Specification Authoring
Writing formal, machine-readable specifications that drive AI-assisted implementation. This skill owns the Specify phase of the SDD pipeline and its output is the prerequisite for all downstream SDD work.
SDD Pipeline Position
INCEPTION → [SPECIFY] → PLAN → TASKS → IMPLEMENT → VERIFY
↑
You are hereThe specification is the single source of truth. Every downstream artifact — task plan, architecture, implementation, tests — derives from and traces back to this document. Ambiguity in the spec propagates as defects in every subsequent phase.
Artifact-Pyramid Output: SPEC.md
The specification documents produced by this skill follow the artifact-pyramid structure:
| Layer | Content | File |
|---|---|---|
| L1 | Executive Summary — one-paragraph scope statement, key stakeholders, overall success criteria | 00-index.md (entry point) |
| L2 | Per-dimension specification — user stories, Gherkin scenarios, edge cases, NFRs, out-of-scope, data contracts | Individual *.spec.md files |
| L3 | Detailed per-story dossiers — full acceptance criteria, interface definitions, data schemas, examples | dossiers/ directory |
| SOURCES | Navigation index linking each L2 dimension to its L3 sources | Footer of each file |
Loading Guidance
| Reference | When to load | File |
|---|---|---|
| Spec Quality Gates | Before delivering any SPEC.md — validates completeness against 7 quality dimensions | references/spec-quality-gates.md |
| Gherkin Patterns | Writing executable scenarios — Given/When/Then structure for specific patterns | references/gherkin-patterns.md |
| Acceptance Criteria Design | Crafting ACs that pass the "no-surprises" test — edge case enumeration, boundary conditions | references/acceptance-criteria-design.md |
| Template | When to use | File |
|---|---|---|
| SPEC.md | Producing a specification document from scratch | templates/SPEC.md |
| Script | When to run | File |
|---|---|---|
spec-quality-check.sh | After authoring a SPEC.md — validates all required sections exist | scripts/spec-quality-check.sh |
Trigger Conditions
Invoke this skill when:
- A new feature, component, or system needs a formal specification before implementation begins
- An existing specification needs refinement or gap analysis
- A vague requirement (ticket, conversation, email) needs to be translated into a structured SDD-ready spec
- The input is a research report, competitive analysis, or user interview transcript that needs distillation into engineering requirements
Output Contract
Every SPEC.md MUST include:
- Problem statement — what problem this solves and why it matters
- Scope boundary — explicit in-scope and out-of-scope
- User stories — prioritized, with links to acceptance criteria
- Acceptance criteria — per-story, framed as Given/When/Then or bulleted pass/fail conditions
- Edge cases — explicit enumeration of boundary conditions, error states, invalid inputs
- Non-functional requirements — performance, security, observability, compliance, accessibility
- Data contracts / interfaces — schemas, APIs, events (can be stubs that get refined in later phases)
The spec is NOT complete until a automated quality check passes (run spec-quality-check.sh).
Show full SKILL.md (256 more words)Show less
SDD Philosophy
Specifications in SDD serve a different purpose than traditional requirements documents. They are not communication artifacts for humans that happen to be read by an AI. They are executable inputs to a code generation pipeline that happen to be readable by humans.
This distinction drives everything about how specs are written:
- Precision over clarity. A spec that is technically precise but dense is better than a spec that reads well but leaves ambiguity. The AI cannot ask for clarification when it encounters a vague phrase — it implements one interpretation at random.
- Completeness over brevity. Every missing acceptance criterion is a missing feature, not a question the implementer will ask. The cost of specifying an edge case up front is minutes. The cost of discovering it in production is hours or days.
- Testability over descriptiveness. An acceptance criterion that cannot be verified (passed or failed) by a deterministic check is not an acceptance criterion — it is a hope. Every AC must produce a binary verdict.
Framework Awareness
This skill is methodology-agnostic at the framework level but follows SDD principles common to all major frameworks:
- GitHub Spec Kit — Four-phase Specify→Plan→Tasks→Implement. The spec produced here fulfills Phase 1 (Specify).
- GSD — Uses PROJECT.md and REQUIREMENTS.md as spec layer. SPEC.md maps to these artifacts.
- BMAD — Role-based specification chain (BA → PRD → Architecture). SPEC.md here aligns with the PRD and Architecture layers.
- Taskmaster AI — PRD-driven. SPEC.md is the structured PRD that Taskmaster parses into task graphs.
- Native Claude Code — CLAUDE.md + spec files. SPEC.md is consumed alongside CLAUDE.md by the implementation agent.
© 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-authoring of magnus919/hermes-profiles.
- SKILL.md
- references/acceptance-criteria-design.md
- references/gherkin-patterns.md
- references/spec-quality-gates.md
- scripts/spec-quality-check.sh
- templates/SPEC.md
Open the folder on GitHubat commit 867a555
Compare with similar skills
Sdd Authoring 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 Authoring this skillmagnus919/hermes-profiles | 289 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Ralph Tui Create JSONsubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| To Prdywwynm/EverythingDone | 144 | 11 repos | ~777 | Automated safety check: Pass | GPL-3.0 | |
| Use Case Writerphucnt-bazone-vietnam/use-case-writer | 143 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
To Prd
ywwynm/EverythingDone
Turn the current conversation context into a PRD and publish it to the project issue tracker.
Use Case Writer
phucnt-bazone-vietnam/use-case-writer
Generate Use Case specifications in English Markdown following the IT BA standard 13-field template (Karl Wiegers / IIBA).
Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
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 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…
Sdd Work Decomposition
magnus919/hermes-profiles
SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria.
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
Categories
Questions about Sdd Authoring
What does Sdd Authoring do?
Specification authoring for AI-native SDD — writes formal specifications in structured formats (Gherkin, user stories, acceptance criteria), enforces spec quality gates, and produces…. Sdd Authoring is an agent skill from magnus919/hermes-profiles.md outputs.
When should I use Sdd Authoring?
Sdd Authoring fits situations like: requirements documents need to be authored from scratch; tasks that involve User stories; tasks that involve Quality gates.
How do I install Sdd Authoring in Claude Code?
Run `npx skills add magnus919/hermes-profiles --skill sdd-authoring -a claude-code`. Or copy the skill folder (skills/sdd-authoring in magnus919/hermes-profiles) into .claude/skills/sdd-authoring in your project. Claude Code loads it when a task matches its description.
How do I install Sdd Authoring in Codex?
Run `npx skills add magnus919/hermes-profiles --skill sdd-authoring -a codex`. Or copy the skill folder (skills/sdd-authoring in magnus919/hermes-profiles) into .agents/skills/sdd-authoring in your project. Codex loads it when a task matches its description.
Can I use Sdd Authoring 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-authoring -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-authoring, .gemini/skills/sdd-authoring, .github/skills/sdd-authoring and .opencode/skills/sdd-authoring in your project.
What does Sdd Authoring need to run?
Going by SKILL.md and its folder, Sdd Authoring needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
Does Sdd Authoring 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 Authoring 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 Authoring use?
Sdd Authoring 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 Authoring use?
About 1.4k tokens (SKILL.md is roughly 5.8k 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 2.6k tokens, read only when the agent opens those files.
What are the alternatives to Sdd Authoring?
Skills that share tags, products or a category with Sdd Authoring: Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars), Ralph Tui Create JSON (subsy/ralph-tui, 2.5k stars) and To Prd (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sdd Authoring?
magnus919 (a GitHub user) maintains it in magnus919/hermes-profiles, which has 289 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.