specdd-adopt
Adopt SpecDD in a Repository
New projects need a clear SpecDD bootstrap before specification work begins. This skill guides Codex, Claude, and Claude Code through CLI setup, update checks, and initial scope reporting.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "specdd-adopt" from https://skillstore.io/skills/specdd-specdd-adopt.md and its manifest at https://skillstore.io/api/skills/specdd-specdd-adopt/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "specdd-adopt". Add SpecDD to this repository and tell me what changed.
Expected outcome:
The repository was not bootstrapped. CLI initialization completed, one root specification was proposed, and no implementation files changed.
Using "specdd-adopt". This project already uses SpecDD. Update the framework files only.
Expected outcome:
The repository was already bootstrapped. The framework update ran through the CLI, and no local specs were modified.
Using "specdd-adopt". Review this repository and suggest the first SpecDD scope.
Expected outcome:
The best starting point is a root project specification. It should cover ownership, references, constraints, and major entry points.
Security Audit
SafeAll static findings are false positives caused by Markdown inline backticks and normal references to SpecDD files, skills, and CLI names. No prompt injection, data exfiltration, hidden command execution, or system reconnaissance intent was found in SKILL.md.
Risk Factors
⚙️ External commands (9)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/specdd-specdd-adopt/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/specdd-specdd-adopt?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/specdd-specdd-adopt?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/specdd-specdd-adopt/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/specdd-specdd-adopt.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
specdd. (2026). specdd-adopt security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/specdd-specdd-adopt/audits/4BibTeX citation
@techreport{specdd-specdd-specdd-adopt-2026,
author = {specdd},
title = {specdd-adopt security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/specdd-specdd-adopt/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "specdd-adopt security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "specdd"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/specdd-specdd-adopt/audits/4"
identifiers:
- type: other
value: "skillstore:specdd-specdd-adopt:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Bootstrap a New Repository
Add SpecDD framework files through the CLI and report the initial adoption scope.
Update Framework Files
Refresh existing SpecDD bootstrap files through the supported CLI workflow.
Plan Initial Specifications
Review repository boundaries and propose a small root specification before authoring child specs.
Try These Prompts
Add SpecDD to this repository. Check whether it is already bootstrapped, use the SpecDD CLI if needed, and report what changed.
Update the SpecDD framework files in this repository. Use the CLI path, do not edit bootstrap files manually, and summarize remaining setup.
Inspect this repository for initial SpecDD boundaries. Propose the smallest useful root spec and child specs before creating any files.
Adopt SpecDD for this mature repository. Limit inspection to top-level structure, manifests, docs, tests, and entry points. Create .sdd files only after approval.
Best Practices
- Confirm whether setup, update, or authoring is the requested task before starting.
- Use the SpecDD CLI for framework files and keep manual edits limited to approved local specs.
- Report bootstrap status, adoption scope, created specs, and any blocked setup steps.
Avoid
- Manually copying bootstrap framework files instead of using the CLI.
- Creating .sdd files before the user approves the adoption scope.
- Changing implementation code during adoption without an explicit user request.