Specdd do

Skill specdd/plugin-cline/skills/specdd-do

SpecDD skills for Cline: on-demand workflows for implementing, reviewing, testing, documenting, and tracing changes in SpecDD projects.

Install

npx -y skills add specdd/plugin-cline --skill specdd-do

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when Cline needs to implement a code, docs, tests, task, or spec change under active SpecDD authority.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.2 KB, as published. Nobody here has run it

SpecDD Do

Use this skill to implement changes under existing SpecDD authority.

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:

.specdd/bootstrap.md
.specdd/bootstrap.project.md, if it exists
.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:

Identify the target path, task, behavior, or changed files.
Resolve the effective spec chain using the active bootstrap rules.
Include same-directory basename specs when applicable.
Walk ancestor specs from the selected content root to the target.
Read explicit References only when they affect the requested work.
Read or reread the specific governing specs needed for the current decision when exact contract text is not already reliable in context.
Identify the nearest local spec that grants write authority before any edit.

Do not infer authority from similar filenames, nearby files, symbols, module names, or conventions unless the active bootstrap or a governing spec explicitly defines that mapping.

Do not reread an entire chain just because a workflow phase changed. Reopen the narrowest relevant spec when you need to apply, quote, compare, authorize, report, or edit against exact text, when the target scope changes, when a governing spec may have changed, or when earlier context came only from CLI output or a summary.

Workflow

Make the smallest correct change inside authority.
Run relevant checks, tests, or validation.
Report specs used, files changed, verification, and remaining uncertainty.

Implementation Rules

Do not edit without clear write authority.
Do not override, loosen, or ignore target project specs.
Do not complete unrelated tasks opportunistically.
Update task status only after implementation and relevant checks are complete.
Prefer project-local tools and conventions.

Stop and ask when a requested change would violate Must not, Forbids, write authority, security constraints, destructive behavior, or public contracts.