specdd-author
Author SpecDD Project Specs
SpecDD projects need specs that match the active bootstrap chain and local ownership rules. This skill guides agents to create or revise scoped .sdd files with clear authority and reporting.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "specdd-author" from https://skillstore.io/skills/specdd-specdd-author.md and its manifest at https://skillstore.io/api/skills/specdd-specdd-author/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-author". Add SpecDD coverage for a new billing notifications area.
Expected outcome:
- Identifies the bootstrap files and nearest governing specs used.
- Creates or updates a focused billing notifications spec.
- Reports the intended governing scope and any unresolved ownership questions.
Using "specdd-author". Clarify ownership rules for files under an existing feature directory.
Expected outcome:
- Reads the relevant spec chain before changing durable project rules.
- Updates ownership language with explicit path-based authority.
- Summarizes changed specs and remaining decisions for the user.
Using "specdd-author". Prepare a governed implementation plan for a service refactor.
Expected outcome:
- Resolves the effective spec chain for the target files.
- Proposes spec changes needed before implementation work.
- Separates confirmed authority from assumptions that require user input.
Security Audit
SafeAll static findings are false positives caused by inline Markdown backticks around SpecDD file names, section names, or related skill names. No command execution instructions, network behavior, credential access, or prompt injection attempts were found in SKILL.md.
Risk Factors
⚙️ External commands (12)
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-author/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/specdd-specdd-author?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/specdd-specdd-author?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/specdd-specdd-author/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/specdd-specdd-author.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-author security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/specdd-specdd-author/audits/5BibTeX citation
@techreport{specdd-specdd-specdd-author-2026,
author = {specdd},
title = {specdd-author security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/specdd-specdd-author/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-author 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-author/audits/5"
identifiers:
- type: other
value: "skillstore:specdd-specdd-author:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Add Local Spec Coverage
Create a focused .sdd file for a project area after reading the governing bootstrap and ancestor specs.
Revise Existing Contracts
Update nearby specs when behavior, ownership, or constraints need clearer local documentation.
Prepare Governed Changes
Resolve the effective spec chain before implementation work so planned edits follow project authority.
Try These Prompts
Use specdd-author to add a concise .sdd spec for this feature area. Read the required bootstrap and governing specs first.
Use specdd-author to revise the nearest relevant .sdd file. Preserve existing authority and make unclear constraints explicit.
Use specdd-author to identify the effective spec chain for these target files and update specs before implementation begins.
Use specdd-author to review whether the current specs grant clear write authority for this change. Report gaps and suggested spec edits.
Best Practices
- Start from the active bootstrap chain before creating or revising durable specs.
- Keep each spec local, behavioral, and limited to useful authority or constraints.
- Report the specs used, files changed, intended scope, and unresolved decisions.
Avoid
- Using the skill in a project that lacks a root SpecDD bootstrap file.
- Changing implementation files when the user only requested specification authoring.
- Inferring write authority from similar filenames or nearby code without explicit spec support.