specd-design

Name: specd-design
Availability: InStock
Author: SpecD

Write and validate design artifacts against schemas with graph impact analysis.

12|Updated Feb 28, 2026

Search Tags:#design #validation #guardrails #specs #graph-analysis #artifact-writing #change-artifact

Ready to run

npx skills add https://github.com/specd-sdd/SpecD --skill specd-design

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specd-design
Source: https://github.com/specd-sdd/SpecD/tree/main/.gemini/skills/specd-design
Command: npx skills add https://github.com/specd-sdd/SpecD --skill specd-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product and engineering teams create and refine formal design artifacts for an active change, ensuring alignment with specs, guardrails, and downstream workflows.

Core Features & Use Cases

Write and validate design artifacts for a change, ensuring they stay in scope and follow defined processes.
Enforce sequential artifact creation, with state-aware guidance, reviews, and optional fast-forward modes.
Leverage the code graph and context to assess impact, dependencies, and risk before finalizing designs.
Use case: when a change requires new design deltas and spec updates, the skill orchestrates artifact creation, validation, and readiness checks.

Quick Start

Begin by loading the change state and context, then start writing the first design artifact.

Frequently Asked Questions about specd-design

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

FAQPage Schema

How do I create design artifacts for a change while enforcing scope guardrails?▼

Design artifacts for a change are created and validated by applying scope guardrails that enforce sequential writes, process artifact instructions, and validate outputs against the schema. This ensures all design deltas stay within defined boundaries.

What is graph-driven impact analysis for design changes?▼

Graph-driven impact analysis for design changes uses the code graph and context to assess dependencies, impact, and risk before finalizing design artifacts. It ensures that design modifications do not introduce unresolved downstream issues.

How do I validate design artifacts against a schema before finalizing a change?▼

Design artifacts are validated against a schema by processing artifact instructions and running readiness checks. This validation happens after sequential artifact creation to ensure spec alignment and compliance before finalizing the design.

When do I need sequential artifact creation with state-aware guidance?▼

Sequential artifact creation with state-aware guidance is needed for end-to-end design sessions requiring explicit artifact management. It enforces ordered writes, review modes, and optional fast-forward modes for complex changes.

Can I use fast-forward modes for design artifact creation and reviews?▼

Fast-forward modes can be used during sequential artifact creation to accelerate reviews. The process applies state-aware guidance and scope guardrails to ensure design artifacts remain compliant even when expediting the workflow.

What are the limitations of managing design artifacts without scope guardrails?▼

Without scope guardrails, design artifact management risks uncontrolled scope creep and unresolved graph impact. Bypassing sequential writes and schema validation can lead to misaligned specs and undetected downstream dependencies.