Automate SDD creation via Unified Scan from five sources.
npx skills add https://github.com/NSEvteev/FullSpec --skill design-create-nsevteev
Please help me install this Agent Skill. Skill: design-create Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/design-create Command: npx skills add https://github.com/NSEvteev/FullSpec --skill design-create-nsevteev
Automates the creation of a comprehensive design document (SDD) using Unified Scan from five sources, then performs Clarify and generates SVC-N sections (nine subsections with an 8:8 mapping), INT-N, and STS-N, including validation artifacts, to streamline cross-service design work.
Run /design-create specs/analysis/0001-auth-oauth2/discussion.md after the WAITING status to start the design creation.
High-intent search queries and answers about installing and using this skill.
Automating design documentation creation involves using Unified Scan to consolidate five sources, generating structured SVC-N, INT-N, and STS-N sections with validation artifacts to streamline cross-service workflows.
A service design specification is a structured document that defines service responsibilities across cross-service workflows. You need it to resolve ambiguities and ensure alignment after a WAITING discussion status.
To resolve ambiguities in cross-service design specifications, perform a Clarify step to allocate service responsibilities and ensure alignment after a WAITING discussion status prior to generating final sections.
Yes, validation artifacts for service design documents are generated automatically alongside SVC-N sections, INT-N, and STS-N components during the Unified Scan process to ensure structured output alignment.
Yes, the workflow explicitly supports SSOT-based documentation by structuring the design output into SVC-N, INT-N, and STS-N sections to maintain a single source of truth across services.
Creating SDDs using Unified Scan requires five specific input sources and a preceding WAITING discussion status; without these prerequisites, the Clarify step and subsequent section generation cannot execute properly.
oogDZGenerate TASK-N development plans with five fields, sub-tasks, and cross-service dependencies.
oogDZGenerate formal design documentation from WAITING parent Discussions for service responsibility allocation.
NSEvteevCreate a structured discussion document with Clarify and validate SSOT instructions.
oogDZValidate design documents against the SDD standard for frontmatter, naming, and required sections.
