maicololiveras/praxisgenai-agent-orchestrator/sdd-init
Claude Code and agent skill by maicololiveras/praxisgenai-agent-orchestrator
- community
Checking that the SKILL.md file is still in the repository.
Initialize Spec-Driven Development context in any project. Detects stack, conventions, and bootstraps the active persistence backend. Trigger: When user wants to initialize SDD in a project, or says "sdd init", "iniciar sdd", "openspec init".
Install
npx vskill@latest install maicololiveras/praxisgenai-agent-orchestrator/sdd-initSKILL.md
The same SKILL.md was published earlier as maicololiveras/praxisgenai-agent-orchestrator/sdd-init.
Purpose
You are a sub-agent responsible for initializing the Spec-Driven Development (SDD) context in a project. You detect the project stack and conventions, then bootstrap the active persistence backend.
Execution and Persistence Contract
Read and follow skills/_shared/persistence-contract.md for mode resolution rules.
- If mode is
engram:
Do NOT create openspec/ directory.
Save project context: `` mem_save( title: "sdd-init/{project-name}", topic_key: "sdd-init/{project-name}", type: "architecture", project: "{project-name}", content: "{detected project context markdown}" ) ` topic_key` enables upserts — re-running init updates the existing context, not duplicates.
(See skills/_shared/engram-convention.md for full naming conventions.)
- If mode is
openspec: Read and followskills/_shared/openspec-convention.md. Run full bootstrap. - If mode is
hybrid: Read and follow BOTH convention files. Run openspec bootstrap AND persist context to Engram. - If mode is
none: Return detected context without writing project files.
What to Do
Step 1: Detect Project Context
Read the project to understand:
- Tech stack (check package.json, go.mod, pyproject.toml, etc.)
- Existing conventions (linters, test frameworks, CI)
- Architecture patterns in use
Step 2: Initialize Persistence Backend
If mode resolves to openspec, create this directory structure:
Step 3: Generate Config (openspec mode)
Based on what you detected, create the config when in openspec mode:
Step 4: Build Skill Registry
Follow the same logic as the skill-registry skill (skills/skill-registry/SKILL.md):
- Scan user skills: glob
*/SKILL.mdacross ALL known skill directories. User-level:~/.claude/skills/,~/.config/opencode/skills/,~/.gemini/skills/,~/.cursor/skills/,~/.copilot/skills/, parent of this skill file. Project-level:.claude/skills/,.gemini/skills/,.agent/skills/,skills/. Skipsdd-*,_shared,skill-registry. Deduplicate by name (project-level wins). Read frontmatter triggers. - Scan project conventions: check for
agents.md,AGENTS.md,CLAUDE.md(project-level),.cursorrules,GEMINI.md,copilot-instructions.mdin the project root. If an index file is found (e.g.,agents.md), READ it and extract all referenced file paths — include both the index and its referenced files in the registry. - ALWAYS write `.atl/skill-registry.md` in the project root (create
.atl/if needed). This file is mode-independent — it's infrastructure, not an SDD artifact. - If engram is available, ALSO save to engram:
mem_save(title: "skill-registry", topic_key: "skill-registry", type: "config", project: "{project}", content: "{registry markdown}")
See skills/skill-registry/SKILL.md for the full registry format and scanning details.
Step 5: Persist Project Context
This step is MANDATORY — do NOT skip it.
If mode is engram:
If mode is openspec or hybrid: the config was already written in Step 3.
If mode is hybrid: also call mem_save as above (write to BOTH backends).
Step 6: Return Summary
Return a structured summary adapted to the resolved mode:
If mode is engram:
Persist project context following skills/_shared/engram-convention.md with title and topic_key sdd-init/{project-name}.
Return:
If mode is openspec:
If mode is none:
Rules
- NEVER create placeholder spec files - specs are created via sdd-spec during a change
- ALWAYS detect the real tech stack, don't guess
- If the project already has an
openspec/directory, report what exists and ask the orchestrator if it should be updated - Keep config.yaml context CONCISE - no more than 10 lines
- 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-init/SKILL.md
Popularity
- 7-day trend score
- 0
Refreshed 3 Oct 2026, a month ago.
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-init)