specdd-refactor
Refactor SpecDD Projects Safely
Spec-driven projects can lose behavior during large structural changes. This skill guides Claude, Codex, and Claude Code through SpecDD-aware refactoring with authority checks and verification.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "specdd-refactor" from https://skillstore.io/skills/specdd-specdd-refactor.md and its manifest at https://skillstore.io/api/skills/specdd-specdd-refactor/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-refactor". A request to move a service into a new package inside an existing SpecDD project.
Expected outcome:
The assistant reports the active bootstrap chain, governing specs, write authority, baseline checks, and a behavior-preserving move plan.
Using "specdd-refactor". A refactor diff that changes tests, documentation, and module paths.
Expected outcome:
The assistant identifies which changes are structural, which specs authorize them, and which verification steps remain.
Using "specdd-refactor". A request that requires a behavior change during a planned refactor.
Expected outcome:
The assistant stops treating the task as pure refactoring and asks for authority covering the behavior change.
Security Audit
SafeAll six static findings are false positives caused by Markdown inline code around SpecDD file names and a referenced skill name. I found no prompt injection, data exfiltration, network access, or shell execution intent in SKILL.md.
Risk Factors
⚙️ External commands (6)
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-refactor/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/specdd-specdd-refactor?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/specdd-specdd-refactor?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/specdd-specdd-refactor/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/specdd-specdd-refactor.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-refactor security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/specdd-specdd-refactor/audits/4BibTeX citation
@techreport{specdd-specdd-specdd-refactor-2026,
author = {specdd},
title = {specdd-refactor security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/specdd-specdd-refactor/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-refactor 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-refactor/audits/4"
identifiers:
- type: other
value: "skillstore:specdd-specdd-refactor:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Restructure a SpecDD module
Plan a module move while preserving contracts, dependencies, tests, and governing specs.
Review refactor authority
Confirm which specs permit edits before changing files across project boundaries.
Align docs and tests after structure changes
Update related specs, documentation, and tests only when structure changes require it.
Try These Prompts
Use specdd-refactor for this SpecDD project. Identify the target files, governing specs, write authority, and baseline checks before editing.
Create a refactor plan for moving this module. Preserve specified behavior, public paths, dependencies, and test coverage.
Review these refactor changes against the active SpecDD chain. List contract risks, missing verification, and files needing spec authority.
Resolve all governing specs for this structural change. Separate pure refactor steps from behavior changes and propose verification for each step.
Best Practices
- Confirm the active bootstrap chain before planning edits.
- Verify write authority for every moved or changed file.
- Run practical baseline checks before and after risky refactor steps.
Avoid
- Using the skill in a project without a root .specdd/bootstrap.md file.
- Changing public behavior while describing the work as only a refactor.
- Moving responsibility across spec boundaries without explicit authority.