スキル一覧に戻る
h2b-dev-studio

sdd-skill-creator

by h2b-dev-studio

웹 기술을 탐색하고 실험하기 위한 개인 공간입니다.

0🍴 0📅 2026年1月20日
GitHubで見るManusで実行

SKILL.md


name: sdd-skill-creator description: | Generate project-specific SDD skills for a repository. Use when: setting up SDD for a new project, customizing SDD for a domain, creating repo-local skills that implement docs/sdd-guidelines.md. Triggers: "create sdd skills", "setup sdd for project", "customize sdd"

SDD Skill Creator

Generate project-specific SDD skills that live in a repository.

Prerequisites

You (the generator) must first:

  1. Read docs/sdd-guidelines.md (especially §1 Artifacts, §9 Customization Points, §10 Multi-Agent)
  2. Have project context available

Generated skills will be self-contained—their users won't need to read Guidelines.

Output Structure

{project}/.sdd/skills/
├── sdd-foundation/SKILL.md
├── sdd-requirements/SKILL.md
├── sdd-design/SKILL.md
├── sdd-verify/SKILL.md
└── sdd-workflow/SKILL.md

Instructions

Step 1: Gather Project Context

QuestionPurposeDefault
Project name?Naming, examples
Domain? (game, API, CLI, etc.)Terminology
Multi-agent?Include §10No
Custom anchor prefixes?Guidelines §9SCOPE-, CONSTRAINT-
REQ ID format?Guidelines §9REQ-{NNN}

Skip questions already answered in conversation.

Step 2: Define Customizations

Fill out the customization record. See templates/customization.yaml.

Step 3: Generate Each Skill

For each skill, create SKILL.md with proper frontmatter and these sections:

SectionContent
CustomizationsFrom Step 2: prefixes, ID formats, terminology
InstructionsGuidelines steps rewritten with project terminology
ExamplesOne complete example using project's domain
VerificationChecklist to validate output

Skill-to-Guidelines Mapping

SkillGuidelines SourceKey Customizations
sdd-foundation§1.1 FoundationAnchor prefixes, domain framing
sdd-requirements§1.2 RequirementsREQ ID format, alignment examples
sdd-design§1.3 Design, §1.4 DecisionsRationale patterns, domain design
sdd-verify§3 VerificationChecklists, gap severity
sdd-workflow§1-5 (full flow)State file, handoff, phase transitions

What "Project-Adapted" Means

Guidelines saysYou write
"Identity Anchors""{Domain} Identity Anchors" with project prefixes
"REQ-{NNN}"Project's REQ ID format with example
"Design item"Domain-specific term (e.g., "endpoint", "mechanic")

If multi-agent: Add §10 coordination to each skill.

Step 4: Write Skills

Create files in .sdd/skills/. Each skill must be:

  • Self-contained — User can follow without reading Guidelines
  • Project-specific — Uses project terminology throughout
  • Guidelines-aligned — Doesn't contradict §1-10
  • Concise — Under 200 lines

Step 5: Verify Generated Skills

For each skill:

  1. Frontmatter has name and description with triggers?
  2. All Step 2 customization values applied?
  3. Complete workflow, no placeholders?
  4. Concrete, domain-relevant example?
  5. Actionable verification checklist?

Step 6: Inform User

Created SDD skills in {project}/.sdd/skills/:

- sdd-foundation   → Foundation documents (§1.1)
- sdd-requirements → Requirements documents (§1.2)
- sdd-design       → Design documents (§1.3)
- sdd-verify       → Integrity verification (§3)
- sdd-workflow     → End-to-end orchestration

Customizations: {prefixes}, {req_format}, multi-agent={yes/no}

Examples

See examples/taskcli.md for a complete walkthrough.

Anti-patterns

Anti-patternProblemFix
Generic skillsNo project valueApply all customizations
Contradict GuidelinesIntegrity violationRe-read source section
Verbose skillsContext wasteKeep < 200 lines
Placeholders leftIncompleteFill all {...} before saving

スコア

総合スコア

50/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です