specdd-cli
Use SpecDD CLI Context
SpecDD projects need targeted context before agents read or change files. This skill guides Claude, Codex, and Claude Code to use the specdd CLI for focused discovery, inspection, and linting.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "specdd-cli" from https://skillstore.io/skills/specdd-specdd-cli.md and its manifest at https://skillstore.io/api/skills/specdd-specdd-cli/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-cli". Resolve context for a component before editing it.
Expected outcome:
A concise report listing relevant specs, reviewed sections, and any authority gaps before code changes.
Using "specdd-cli". Inspect a directory that may need a new spec.
Expected outcome:
A mapped summary of nearby specs, their selected sections, and the likely placement boundary.
Using "specdd-cli". Lint edited SpecDD files.
Expected outcome:
A validation summary that states whether lint passed, names files with diagnostics, and identifies remaining fixes.
Security Audit
SafeThe static alerts are false positives from Markdown backticks, documented CLI examples, and local path descriptions. The skill guides explicit local specdd CLI use, requires operator intent for setup or updates, and forbids automatic installation. No prompt injection, credential access, network exfiltration, or malicious intent was found in SKILL.md.
Risk Factors
โ๏ธ External commands (85)
๐ Filesystem access (1)
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-cli/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/specdd-specdd-cli?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/specdd-specdd-cli?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/specdd-specdd-cli/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/specdd-specdd-cli.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-cli security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/specdd-specdd-cli/audits/5BibTeX citation
@techreport{specdd-specdd-specdd-cli-2026,
author = {specdd},
title = {specdd-cli security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/specdd-specdd-cli/audits/5},
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-cli security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "specdd"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/specdd-specdd-cli/audits/5"
identifiers:
- type: other
value: "skillstore:specdd-specdd-cli:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Prepare an implementation task
Resolve the governing specs for a target file before editing code.
Author or update specs
Inspect nearby SpecDD files to choose the right boundary for a new or changed spec.
Validate contract changes
Lint edited .sdd files and summarize remaining diagnostics before completion.
Try These Prompts
Use the SpecDD CLI to resolve context for [target path]. Summarize governing specs before changing files.
Inspect [path] with focused sections. Report which specs exist and which sections matter for this task.
Lint the edited SpecDD files. Explain whether validation passed and list any diagnostics that still need work.
When I explicitly ask, update this project with the SpecDD CLI. Report changed bootstrap files and reread affected context.
Best Practices
- Run CLI commands from the project root when possible.
- Use section filters to keep output focused.
- Lint edited specs before reporting completion.
Avoid
- Do not use this skill when the project lacks .specdd/bootstrap.md.
- Do not auto-install specdd when the CLI is missing.
- Do not treat resolve output as permission to edit files.