sdd-init
Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.
- License 许可
- MIT
- 最近更新
- 2026-07-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- sdd-init
- license
- MIT
- metadata
- { "author": "gentleman-programming", "version": "3.0", "delegate_only": true }
- description
- Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.
- user-invocable
- false
- disable-model-invocation
- true
02 资源文件 1
- 参考文档references/init-details.md4.6 KB
03 SKILL.md 正文
ORCHESTRATOR GATE: If you loaded this skill via the
skill()tool, you are the ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate to the dedicatedsdd-initsub-agent using your platform's delegation primitive (e.g.,task(...), sub-agent invocation, etc.). This skill is for EXECUTORS only.
Activation Contract
Run this phase when the orchestrator/user asks to initialize SDD in a project. You are the phase executor: do the work yourself, do not delegate, and do not behave like the orchestrator.
Hard Rules
- Detect the real stack, conventions, architecture, testing tools, and persistence mode; never guess.
- In
engrammode, do not createopenspec/. - In
openspecmode, follow../_shared/openspec-convention.mdand write file artifacts. - In
hybridmode, write both openspec files and Engram observations. - Always persist testing capabilities separately as
sdd/{project}/testing-capabilitiesoropenspec/config.yamltesting:. - Always build
.atl/skill-registry.md; also saveskill-registryto Engram when available. - Use
capture_prompt: falsefor automated SDD/config saves when supported; omit it if the tool schema lacks it. - If
openspec/already exists, report what exists and ask before updating it.
Decision Gates
| Input | Action |
|---|---|
mode=engram |
Save context and capabilities to Engram only. |
mode=openspec |
Create/update openspec bootstrap files only. |
mode=hybrid |
Do both Engram and openspec persistence. |
mode=none |
Return detected context only; write no SDD artifacts except registry if required. |
| strict TDD marker/config found | Use that value. |
| no marker/config but test runner exists | Default strict_tdd: true. |
| no test runner | Set strict_tdd: false and explain unavailable. |
Execution Steps
- Inspect project files (
package.json,go.mod,pyproject.toml, CI, lint/test config) and summarize stack/conventions. - Detect test runner, test layers, coverage, linter, type checker, and formatter.
- Resolve Strict TDD from agent marker,
openspec/config.yaml, detected runner fallback, or no-runner fallback. - Initialize persistence for the resolved mode.
- Build
.atl/skill-registry.mdusing the skill-registry scan rules. - Persist testing capabilities and project context.
- Return the structured initialization envelope.
Output Contract
Return status, executive_summary, artifacts, next_recommended, and risks. Include project, stack, persistence mode, Strict TDD status, testing capability table, saved observation IDs/paths, registry path, and next /sdd-explore or /sdd-new step.
References
- references/init-details.md — detection checklist, Engram payloads, config skeleton, and output templates.
../_shared/engram-convention.md— Engram artifact naming.../_shared/openspec-convention.md— openspec layout and rules.
04 同仓库更多 Skills
zustand-5
Zustand 5 state management patterns. Trigger: When managing React state with Zustand.
zod-4
Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
web-quality-audit
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.