specdd-docs
Document SpecDD Projects From Specs
Spec-driven projects need documentation that matches current contracts. This skill guides Claude, Codex, and Claude Code to update docs from active SpecDD specs.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "specdd-docs" from https://skillstore.io/skills/specdd-specdd-docs.md and its manifest at https://skillstore.io/api/skills/specdd-specdd-docs/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-docs". Update the README section for the invitation flow from active SpecDD specs.
Expected outcome:
The invitation flow section is updated, the governing specs are listed, and one underspecified expiration rule is reported.
Using "specdd-docs". Review the install guide against the changed setup specs.
Expected outcome:
The review identifies two unsupported claims, one missing constraint, and the spec files used for the comparison.
Using "specdd-docs". Write docs for the new export behavior without expanding the contract.
Expected outcome:
The draft explains the specified export behavior, avoids unsupported guarantees, and notes tests that support the documented flow.
Security Audit
SafeAll eight static findings are false positives caused by Markdown inline code around file paths and skill names in SKILL.md. I found no executable shell or Ruby code, prompt injection attempt, network access, or data exfiltration intent in the reviewed file.
Risk Factors
⚙️ External commands (8)
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-docs/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/specdd-specdd-docs?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/specdd-specdd-docs?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/specdd-specdd-docs/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/specdd-specdd-docs.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-docs security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/specdd-specdd-docs/audits/5BibTeX citation
@techreport{specdd-specdd-specdd-docs-2026,
author = {specdd},
title = {specdd-docs security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/specdd-specdd-docs/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-docs 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-docs/audits/5"
identifiers:
- type: other
value: "skillstore:specdd-specdd-docs:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Update Feature Documentation
Refresh user-facing docs after a SpecDD contract changes, while preserving documented constraints.
Prepare Implementation Notes
Create concise technical docs that explain specified behavior without adding unsupported promises.
Review Documentation Scope
Check whether requested documentation edits have authority from the active spec chain.
Try These Prompts
Use specdd-docs to update the documentation for [feature]. Read the active bootstrap and governing specs before editing.
Use specdd-docs to draft documentation for [behavior]. Source every claim from the active specs and implementation evidence.
Use specdd-docs to review [document]. Identify claims that are unsupported, outdated, or missing important constraints.
Use specdd-docs to determine which specs govern [target path]. Report the write authority, docs to change, and any underspecified behavior.
Best Practices
- Confirm the project has a root .specdd/bootstrap.md before using this skill.
- Resolve the governing spec chain and write authority before editing documentation.
- Report the specs used, documents changed, and any behavior that remains underspecified.
Avoid
- Using this skill in a non-SpecDD project without an explicit adoption request.
- Adding promises, APIs, or workflows that are not supported by specs or implementation.
- Inferring write authority from nearby files, names, or conventions alone.