Agent skill · writing content · aiskillstore
specdd-explain
Use when Agent needs to explain a SpecDD spec, target, behavior, or effective spec chain without editing it.
Why this skill is useful
Provides domain-specific knowledge on SpecDD contracts and effective spec chains that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
SpecDD Explain Use this skill to explain SpecDD contracts to a human. Keep the explanation succinct and clear while including enough depth to understand the feature, module, workflow, or file governed by the spec. Skill Scope Use this skill only for projects that already have a root .specdd/bootstrap.md and are therefore SpecDD projects. If .specdd/bootstrap.md is missing, do not continue with this skill. Use specdd-adopt only when the operator explicitly asks to add or adopt SpecDD in a new or existing non-SpecDD project. Bootstrap Resolution Ensure you know the active bootstrap chain for the target project. If it is not already reliable in the current context, read bootstrap files in this exact order: 1. .specdd/bootstrap.md 2. .specdd/bootstrap.project.md, if it exists 3. .specdd/bootstrap.local.md, if it exists Apply them in that order. Later files may narrow or specialize earlier rules, but must not silently weaken project contracts, inherited constraints, or write authority. Do not reread bootstrap files merely because another SpecDD skill or workflow phase starts. Reread the specific bootstrap file only when the active project root changes, a bootstrap file may have changed, or you need exact bootstrap text for a decision, quote, comparison, authorization, or report. Spec Chain Resolution Before planning, editing, reviewing, testing, or reporting on a target, ensure the effective spec chain for that target is known: 1. Identify the target path, task, behavior, or changed files. 2. Resolve the effective spec chain using the active bootstrap rules. 3. Include same-directory basename specs when applicable. 4. Walk ancestor specs from the selected content root to the target. 5. Read explicit References only when they affect the requested work. 6. Read or reread the specific governing specs needed for the current decision when exact contract text is not already reliable in context. 7. Identify the nearest local spec that grants write authority before any edit. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/specdd-explain