maicololiveras/praxisgenai-agent-orchestrator/sdd-design
Claude Code and agent skill by maicololiveras/praxisgenai-agent-orchestrator
- community
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 maicololiveras/praxisgenai-agent-orchestrator/sdd-designSKILL.md
The same SKILL.md was published earlier as maicololiveras/praxisgenai-agent-orchestrator/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:
Read dependencies (two-step — search returns truncated previews):
mem_search(query: "sdd/{change-name}/proposal", project: "{project}")→ get observation IDmem_get_observation(id: {id from step 1})→ full proposal content (REQUIRED)mem_search(query: "sdd/{change-name}/spec", project: "{project}")→ get observation ID (optional — may not exist if running in parallel with sdd-spec)- If found:
mem_get_observation(id: {id from step 3})→ full spec content
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 followskills/_shared/openspec-convention.md. - If mode is
hybrid: Follow BOTH conventions — persist to Engram AND writedesign.mdto 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.
- Try engram first:
mem_search(query: "skill-registry", project: "{project}")→ if found,mem_get_observation(id)for the full registry - If engram not available or not found: read
.atl/skill-registry.mdfrom the project root - 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
Create the design document:
Design Document Format
Step 4: Persist Artifact
This step is MANDATORY — do NOT skip it.
If mode is engram:
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:
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.designfromopenspec/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, andrisks
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/sdd-design/SKILL.md
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
[](https://verified-skill.com/skills/maicololiveras/praxisgenai-agent-orchestrator/sdd-design)