design-create

Generate formal design documentation from WAITING parent Discussions for service responsibility allocation.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill design-create-oogdz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-create
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/design-create
Command: npx skills add https://github.com/oogDZ/2 --skill design-create-oogdz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Этот навык автоматизирует создание документа проектирования (SDD) на основе обсуждения, когда обсуждение переходит в статус WAITING, чтобы перераспределить ответственность между сервисами и ускорить согласование архитектуры.

Core Features & Use Cases

  • Автоматическое формирование разделов SVC-N (9 подсекций) и маппинг к INT-N и STS-N на основе исходных материалов.
  • Интеграция Clarify и валидация артефактов согласно SSOT-инструкциям.
  • Применение после утверждения Discussion для распределения ответственности между сервисами.

Quick Start

Укажите путь к parent Discussion в WAITING и запустите команду /design-create с указанным путём.

Frequently Asked Questions about design-create

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

FAQPage Schema
How do I generate design documentation from a discussion to allocate service responsibilities?

You can generate design documentation by running an automated command against a parent Discussion in WAITING status, which extracts the conversation to allocate responsibilities between services. This automatically structures cross-service workflows into standardized architecture sections.

What is the best way to map cross-service integrations and validations in architecture specifications?

The best way to map cross-service integrations in architecture specifications is to automatically generate SVC-N sections alongside INT-N integrations and STS-N validations. This ensures formal artifacts are accurately mapped directly from source discussion materials.

How does SSOT validation work when creating formal design documents?

SSOT validation for formal design documents works by enforcing Single Source of Truth instructions during the generation process. It automatically validates the generated cross-service architecture outputs against established project standards to ensure structural compliance.

Can I use discussion artifacts to clarify architecture details before finalizing a design specification?

Yes, you can clarify architecture details before finalizing a design specification by using integrated Clarify steps. The workflow supports resolving ambiguities during document generation to ensure the finalized architecture outputs are validated against project standards.

Do I need a parent Discussion in WAITING status to start cross-service design document generation?

Yes, a parent Discussion in WAITING status is required to start cross-service design document generation. This specific status indicates the initial discussion is ready to be transitioned into a formal specification to distribute responsibilities across services.