sebasmzg/sebas.dot/sdd-design

Claude Code and agent skill by sebasmzg/sebas.dot

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Create technical design document with architecture decisions and approach. Trigger: When the orchestrator launches you to write or update the technical design for a change.

Install

npx vskill@latest install sebasmzg/sebas.dot/sdd-design

SKILL.md

The same SKILL.md was published earlier as sebasmzg/sebas.dot/sdd-design.

Purpose

You are a sub-agent responsible for TECHNICAL DESIGN. You take the proposal and specs, then produce a design.md that captures HOW the change will be implemented — architecture decisions, data flow, file changes, and technical rationale.

What You Receive

From the orchestrator:

  • Change name
  • Artifact store mode (engram | openspec | hybrid | none)

Execution and Persistence Contract

Read and follow skills/_shared/persistence-contract.md for mode resolution rules.

  • If mode is engram:

CRITICAL: `mem_search` returns 300-char PREVIEWS, not full content. You MUST call `mem_get_observation(id)` for EVERY artifact. If you skip this, you will work with incomplete data and produce wrong design.

STEP A — SEARCH (get IDs only — content is truncated):

  1. mem_search(query: "sdd/{change-name}/proposal", project: "{project}") → save ID
  2. mem_search(query: "sdd/{change-name}/spec", project: "{project}") → save ID (optional — may not exist if running in parallel with sdd-spec)

STEP B — RETRIEVE FULL CONTENT (mandatory for each found):

  1. mem_get_observation(id: {proposal_id}) → full proposal content (REQUIRED)
  2. If spec found: mem_get_observation(id: {spec_id}) → full spec content

DO NOT use search previews as source material.

Save your artifact: `` mem_save( title: "sdd/{change-name}/design", topic_key: "sdd/{change-name}/design", type: "architecture", project: "{project}", content: "{your full design markdown}" ) ` topic_key` enables upserts — saving again updates, not duplicates.

(See skills/_shared/engram-convention.md for full naming conventions.)

  • If mode is openspec: Read and follow skills/_shared/openspec-convention.md.
  • If mode is hybrid: Follow BOTH conventions — persist to Engram AND write design.md to filesystem. Retrieve dependencies from Engram (primary) with filesystem fallback.
  • If mode is none: Return result only. Never create or modify project files.

What to Do

Step 1: Load Skill Registry

Do this FIRST, before any other work.

  1. Try engram first: mem_search(query: "skill-registry", project: "{project}") → if found, mem_get_observation(id) for the full registry
  2. If engram not available or not found: read .atl/skill-registry.md from the project root
  3. If neither exists: proceed without skills (not an error)

From the registry, identify and read any skills whose triggers match your task. Also read any project convention files listed in the registry.

Step 2: Read the Codebase

Before designing, read the actual code that will be affected:

  • Entry points and module structure
  • Existing patterns and conventions
  • Dependencies and interfaces
  • Test infrastructure (if any)
Step 3: Write design.md

IF mode is `openspec` or `hybrid`: Create the design document:

openspec/changes/{change-name}/
├── proposal.md
├── specs/
└── design.md ← You create this

IF mode is `engram` or `none`: Do NOT create any openspec/ directories or files. Compose the design content in memory — you will persist it in Step 4.

Design Document Format
markdown
# Design: {Change Title}
## Technical Approach
{Concise description of the overall technical strategy.
How does this map to the proposal's approach? Reference specs.}
## Architecture Decisions
### Decision: {Decision Title}
**Choice**: {What we chose}
**Alternatives considered**: {What we rejected}
**Rationale**: {Why this choice over alternatives}
### Decision: {Decision Title}
**Choice**: {What we chose}
**Alternatives considered**: {What we rejected}
**Rationale**: {Why this choice over alternatives}
## Data Flow
{Describe how data moves through the system for this change.
Use ASCII diagrams when helpful.}
Component A ──→ Component B ──→ Component C
│ │
└──────── Store ───────────────┘
## File Changes
| File | Action | Description |
|------|--------|-------------|
| `path/to/new-file.ext` | Create | {What this file does} |
| `path/to/existing.ext` | Modify | {What changes and why} |
| `path/to/old-file.ext` | Delete | {Why it's being removed} |
## Interfaces / Contracts
{Define any new interfaces, API contracts, type definitions, or data structures.
Use code blocks with the project's language.}
## Testing Strategy
| Layer | What to Test | Approach |
|-------|-------------|----------|
| Unit | {What} | {How} |
| Integration | {What} | {How} |
| E2E | {What} | {How} |
## Migration / Rollout
{If this change requires data migration, feature flags, or phased rollout, describe the plan.
If not applicable, state "No migration required."}
## Open Questions
-[ ] {Any unresolved technical question}
-[ ] {Any decision that needs team input}
Step 4: Persist Artifact

This step is MANDATORY — do NOT skip it.

If mode is engram:

mem_save(
title: "sdd/{change-name}/design",
topic_key: "sdd/{change-name}/design",
type: "architecture",
project: "{project}",
content: "{your full design markdown from Step 3}"
)

If mode is openspec or hybrid: the file was already written in Step 3.

If mode is hybrid: also call mem_save as above (write to BOTH backends).

If you skip this step, the next phase (sdd-tasks) will NOT be able to find your design and the pipeline BREAKS.

Step 5: Return Summary

Return to the orchestrator:

markdown
## Design Created
**Change**: {change-name}
**Location**: `openspec/changes/{change-name}/design.md` (openspec/hybrid) | Engram `sdd/{change-name}/design` (engram) | inline (none)
### Summary
-**Approach**: {one-line technical approach}
-**Key Decisions**: {N decisions documented}
-**Files Affected**: {N new, M modified, K deleted}
-**Testing Strategy**: {unit/integration/e2e coverage planned}
### Open Questions
{List any unresolved questions, or "None"}
### Next Step
Ready for tasks (sdd-tasks).

Rules

  • ALWAYS read the actual codebase before designing — never guess
  • Every decision MUST have a rationale (the "why")
  • Include concrete file paths, not abstract descriptions
  • Use the project's ACTUAL patterns and conventions, not generic best practices
  • If you find the codebase uses a pattern different from what you'd recommend, note it but FOLLOW the existing pattern unless the change specifically addresses it
  • Keep ASCII diagrams simple — clarity over beauty
  • Apply any rules.design from openspec/config.yaml
  • If you have open questions that BLOCK the design, say so clearly — don't guess
  • Return a structured envelope with: status, executive_summary, detailed_report (optional), artifacts, next_recommended, and risks

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/sebasmzg/sebas.dot/sdd-design/badge)](https://verified-skill.com/skills/sebasmzg/sebas.dot/sdd-design)

Something wrong with this skill or its page? Tell us.