sync-dev-org/sdd-log
framework/claude/skills/sdd-log/SKILL.md
Record decisions, issues, and knowledge to session YAML files (.sdd/session/). Use this skill whenever the user wants to log, record, track, or remember something. Triggers: /sdd-log, issue, 問題, バグ, bug, 機能, feature, 改善, enhancement, 判断, 決定, decision, 覚えて, remember, knowledge, record, log, track, 登録, 記録. Subcommands: decision, issue, knowledge, resolve, update, flush. Make sure to use this skill for ANY request to record project decisions, report bugs or issues, track feature requests, store knowledge or learnings, resolve issues, or flush unpersisted session data to YAML files.
testing
Updated Apr 15, 2026
$ install --global
skillsauthnpx skillsauth add sync-dev-org/sync-sdd sdd-logInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 4:09 AM41.3s1 file scanned
SKILL.md
- name:
- sdd-log
- description:
- Record decisions, issues, and knowledge to session YAML files (.sdd/session/). Use this skill whenever the user wants to log, record, track, or remember something. Triggers: /sdd-log, issue, 問題, バグ, bug, 機能, feature, 改善, enhancement, 判断, 決定, decision, 覚えて, remember, knowledge, record, log, track, 登録, 記録. Subcommands: decision, issue, knowledge, resolve, update, flush. Make sure to use this skill for ANY request to record project decisions, report bugs or issues, track feature requests, store knowledge or learnings, resolve issues, or flush unpersisted session data to YAML files.
- allowed-tools:
- Bash, Read, Edit, Write, Glob
- argument-hint:
- decision|issue|knowledge|resolve|update|flush <args>
<instructions>
You are the sdd-log skill. You record session data (decisions, issues, knowledge) to YAML files under `.sdd/session/`.
resolve
update
Subcommands
| Subcommand | Target File | Purpose |
|------------|-------------|---------|
| decision | decisions.yaml | Record an explicit choice or direction |
| issue | issues.yaml | Record a bug, feature request, or enhancement |
| knowledge | knowledge.yaml | Record a reusable insight or learning |
| resolve <ID> | issues.yaml | Mark an issue as resolved |
| update <ID> <field=value> | Auto-detect by prefix | Update any entry field |
| flush | All three files | Persist unpersisted items from conversation |
Dispatch
Parse the subcommand from the user's message, then execute:
decision / issue / knowledge
Read .sdd/lib/prompts/log/record.md and follow its instructions to record the entry.
flush
Read .sdd/lib/prompts/log/flush.md and follow its instructions to flush unpersisted items.
resolve <ID>
- Validate the ID starts with
I. If not, report error: "Only issues (I-prefix) can be resolved." - Read
.sdd/session/issues.yaml, find the entry with matching ID. - If not found, report error: "Issue {ID} not found."
- If already resolved, report: "Issue {ID} is already resolved."
- Get timestamp via Bash:
date +%Y-%m-%dT%H:%M:%S%z - Use Edit to update the entry:
- Change
status: "open"→status: "resolved" - Add
resolution: "{resolution text}"after thesource:line - Add
resolved_at: "{timestamp}"aftercreated_at:
- Change
- Ask the user for the resolution text if not provided.
update <ID> <field=value>
- Auto-detect file by ID prefix:
D→ decisions.yaml,I→ issues.yaml,K→ knowledge.yaml. - Read the file under
.sdd/session/, find the entry with matching ID. - If not found, report error.
- Validate the field name against the schema:
- Decision: status, severity, summary, detail, source
- Issue: type, status, severity, summary, detail, source, resolution, resolved_at
- Knowledge: status, severity, summary, detail, source
- Use Edit to update the specific field value.
- Confirm the change. </instructions>
Related Skills
sync-dev-org/framework/claude/skills/sdd-steering
tools
VerifiedTrustedCommunity
--- name: sdd-steering description: Set up project-wide context (create, update, delete, custom) allowed-tools: Bash, Glob, Grep, Read, Write, Edit, Skill argument-hint: [-y] [custom] --- # SDD Steering (Unified) <instructions> ## Core Task Manage project steering documents. Lead handles directly (no SubAgent dispatch needed) since it requires user interaction. **Before any steering operation**, read `{{SDD_DIR}}/settings/rules/agent/steering-principles.md` and apply its principles (content
SKILL.mdUpdated Apr 15, 2026
sync-dev-org/framework/claude/skills/sdd-status
tools
VerifiedTrustedCommunity
--- name: sdd-status description: Check progress and analyze downstream impact allowed-tools: Read, Glob, Grep argument-hint: [feature-name] [--impact] --- # SDD Status (Unified) <instructions> ## Core Task Display comprehensive status for specifications and optionally analyze downstream impact of changes. Lead handles directly (read-only, no SubAgent needed). ## Step 1: Parse Arguments ``` $ARGUMENTS = "" → Overall roadmap + all specs progress $ARGUMENTS = "{feature}"
SKILL.mdUpdated Apr 15, 2026
sync-dev-org/sdd-start
tools
VerifiedTrustedCommunity
Session start — invoke on "再開", "continue", "resume", or at every session start
SKILL.mdUpdated Apr 15, 2026
sync-dev-org/sdd-roadmap
content-media
VerifiedTrustedCommunity
Unified spec lifecycle (design, impl, review, roadmap management)
SKILL.mdUpdated Apr 15, 2026