doc-bd-sec

Generate and update BD-SEC security design documents for the diopside project.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-bd-sec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-bd-sec
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-bd-sec
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-bd-sec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires auto_link_glossary.py, validate_vault.py, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you create and update security design documents (BD-SEC) for the diopside project, ensuring compliance with Obsidian operational guidelines and clearly defining threat boundaries, defense strategies, and auditing perspectives.

Core Features & Use Cases

  • Structured Security Documentation: Generates documents adhering to specific frontmatter and content requirements for security design.
  • Threat Boundary Definition: Clearly outlines the scope of security for data collection, storage, distribution, and operation.
  • Use Case: When designing the security for the diopside YouTube archive system, use this Skill to document the authentication and authorization boundaries, input validation policies, and secret management strategies according to project standards.

Quick Start

Use the doc-bd-sec skill to create a new security design document for the public YouTube data collection API.

Frequently Asked Questions about doc-bd-sec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate security design documents for system architecture in Obsidian?

Security design documentation defines threat boundaries, defense strategies, and auditing perspectives for system architecture. It ensures compliance with frontmatter requirements and content structure standards within Obsidian vaults.

What is the best way to document threat boundaries and defense strategies for a YouTube archive system?

Documenting threat boundaries involves outlining security scopes for data collection, storage, distribution, and operation. You define authentication boundaries, input validation policies, and secret management strategies according to project standards.

How do I ensure my security design documentation complies with Obsidian operational guidelines?

Ensuring compliance with Obsidian operational guidelines requires validating vault structure and frontmatter. You use validation scripts to check that security design documents adhere to specific content requirements and automated glossary linking rules.

Does this approach support defining compliance and auditing perspectives for data storage APIs?

Yes, defining compliance and auditing perspectives for data storage APIs is supported. The documentation process structures security designs by outlining security operations and defense strategies for public data collection endpoints.