specdd-plan
Plan SpecDD Work Safely
SpecDD projects need clear scope and authority before implementation starts. This skill guides Claude, Codex, and Claude Code through focused planning.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "specdd-plan" from https://skillstore.io/skills/specdd-specdd-plan.md and its manifest at https://skillstore.io/api/skills/specdd-specdd-plan/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-plan". Plan a change to update validation behavior in a SpecDD project.
Expected outcome:
A scoped plan naming the target, governing specs, allowed files, validation risks, blockers, and likely tests.
Using "specdd-plan". Determine whether an agent can edit a module under SpecDD rules.
Expected outcome:
An authority summary that cites the needed spec chain and lists unresolved permission questions.
Using "specdd-plan". Prepare a handoff plan for a cross-directory feature.
Expected outcome:
A practical implementation path with affected areas, required constraints, verification steps, and open decisions.
Security Audit
SafeAll eight static findings are false positives caused by Markdown inline code spans in SKILL.md. I found no prompt injection, data exfiltration intent, or executable command behavior in the reviewed skill text.
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-plan/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/specdd-specdd-plan?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/specdd-specdd-plan?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/specdd-specdd-plan/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/specdd-specdd-plan.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-plan security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/specdd-specdd-plan/audits/4BibTeX citation
@techreport{specdd-specdd-specdd-plan-2026,
author = {specdd},
title = {specdd-plan security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/specdd-specdd-plan/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-plan 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-plan/audits/4"
identifiers:
- type: other
value: "skillstore:specdd-specdd-plan:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Plan a SpecDD change
Resolve the governing specs and authority before asking an agent to edit files.
Review implementation scope
Identify affected files, constraints, risks, and verification before work begins.
Prepare agent handoff
Create a concise plan that another AI coding agent can follow safely.
Try These Prompts
Use specdd-plan to plan this small change. Identify the target scope, governing specs, write authority, and verification.
Use specdd-plan to resolve whether this target has write authority. List blockers and questions before any edits.
Use specdd-plan for this feature request. Summarize constraints, likely changed files, risks, and the smallest safe implementation path.
Use specdd-plan to analyze this cross-area request. Compare spec constraints, identify conflicts, and define required verification.
Best Practices
- Start with the exact target path, behavior, or task before planning.
- Read only the governing specs needed for the current decision.
- Record blockers when authority or verification is unclear.
Avoid
- Do not use this skill to adopt SpecDD in a non-SpecDD project.
- Do not infer write authority from nearby filenames or conventions.
- Do not turn the plan into a broad refactor proposal.