Sdd spec kit

Skill Xopoko/plug-n-skills/plugins/spec-driven-development/skills/sdd-spec-kit

Ready-to-install skills and plugins for Codex, Claude Code, and AI coding agents: practical workflows for app delivery, architecture, research, design, and agent tooling.

Install

npx -y skills add Xopoko/plug-n-skills --skill sdd-spec-kit

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

9 stars9 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 GitHub Spec Kit projects and commands, including constitution, specify, clarify, plan, tasks, analyze, implement, extensions, and presets.

SKILL.md

2.6 KB, 571 tokens by cl100k_base, as published. Nobody here has run it

SDD Spec Kit

Use for GitHub Spec Kit, Specify CLI, /speckit.*, $speckit-*, .specify/, extensions, presets, or Spec Kit command behavior.

Source Model

Project workspace is source of truth. Upstream https://github.com/github/spec-kit and any user-provided Spec Kit reference checkout are references unless the user asks to edit Spec Kit itself.

Preflight

PowerShell: use $env:PLUGIN_ROOT for $PLUGIN_ROOT command paths.

python3 "$PLUGIN_ROOT/scripts/sdd_surface_audit.py" <repo> --json
git status --short

Check .specify/, .specify/feature.json, .specify/memory/constitution.md, specs/*/{spec.md,plan.md,tasks.md}, and .specify/extensions.yml. State any init/install/upgrade/fetch before running it.

Command Map

Follow project command files when present; otherwise use this layout:

Constitution: .specify/memory/constitution.md
Specify: specs/<feature>/spec.md plus specs/<feature>/checklists/requirements.md
Clarify: resolve [NEEDS CLARIFICATION]
Plan: plan.md, research.md, data-model.md, contracts/, quickstart.md, risk/evidence profile
Tasks: tasks.md with dependency order, requirement links, paths, verification, expected evidence
Analyze: read-only artifact consistency
Implement: execute tasks, update status, verify

Extensions

For .specify/extensions.yml: read relevant before_*/after_*; skip disabled hooks; do not evaluate non-empty conditions yourself. Mandatory hooks surface EXECUTE_COMMAND: <command> and wait when supported. Optional hooks are reported unless requested.

Gates

spec.md: no implementation leakage unless template allows; sources/assumptions/ambiguity/review gaps visible for high-impact requirements.
plan.md: decisions, rationale, alternatives, constitution gate, risk/evidence profile, traceability strategy.
tasks.md: IDs, story labels when applicable, paths, dependencies, independent validation.
Strict/regulated work: evidence ledger such as evidence.md, validation.md, proof.md, or equivalent in quickstart.md/tasks.md.
LLM self-review, model confidence, or context-free LLM-as-a-judge is advisory only.
Run python3 "$PLUGIN_ROOT/scripts/sdd_traceability_check.py" <repo> --json before implementation and before claiming done.

Report

Return active feature directory, changed Spec Kit artifacts, unresolved risks, validation commands/outcomes, evidence updates, and next phase.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.