Assists in writing and verifying behavior specs for software design documentation.
Install
mkdir -p .claude/skills/dude-spec && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12612" && unzip -o skill.zip -d .claude/skills/dude-spec && rm skill.zipInstalls to .claude/skills/dude-spec
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create or edit spec files with behavior contracts for dude SDD workflow.Key capabilities
- →Create or edit spec files with behavior contracts.
- →Scan spec files to see current anchors.
- →Write spec with `## [ID] Title` and `contract` blocks.
- →Identify what needs code anchors using `get_drift_report()`.
- →Write code with `# @anchor ID [behavior_props]` on definitions.
- →Verify behavior matches the contract using `verify_behavior(id)`.
How it works
The skill facilitates the creation and editing of spec files by enforcing a specific format for behavior contracts and providing tools to scan, report drift, and verify code against these contracts.
Inputs & outputs
When to use dude-spec
- →Writing a feature spec
- →Defining behavior contracts
- →Verifying implementation against spec
About this skill
Create / Edit Spec Files
Target
Work on: $ARGUMENTS
If no argument, use spec/SPEC.md.
Spec Format
## [PREFIX-NNN] Feature Title
Description of the feature.
```contract
role: adapter
effects: network + state
concurrency: safe
complexity: O(1)
pre: connection_established()
post: result_valid(result)
invariant: count <= max
```
Anchor ID Convention
- Format:
PREFIX-NNN(uppercase, hyphen, zero-padded) - Prefix = module domain: EVAL, GATE, CLI, WATCH, LSP, CONFIG...
Steps
- Read the spec file (or confirm it doesn't exist)
- Call
scan_spec_file(path)to see current anchors - Write spec with
## [ID] Title+```contractblock - Call
get_drift_report()to see what needs code anchors - Write code with
# @anchor ID [behavior_props]on the definition - Call
verify_behavior(id)to confirm behavior matches
When not to use it
- →When the user wants to perform actions outside of spec file creation or editing.
- →When the user does not provide a `spec-file-path` argument and the default `spec/SPEC.md` is not desired.
Limitations
- →It is disabled for direct model invocation.
- →It requires a specific spec format with `## [ID] Title` and `contract` blocks.
- →It uses `PREFIX-NNN` as the anchor ID convention.
How it compares
This skill integrates behavior contracts directly into spec files and provides tools for syncing code to documentation, offering a more rigorous approach to specification and verification than traditional documentation methods.
Compared to similar skills
dude-spec side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| dude-spec (this skill) | 0 | 4mo | No flags | Intermediate |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| repo-research-analyst | 1 | 6mo | Review | Intermediate |
| c4-component | 1 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
repo-research-analyst
parcadei
Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase
c4-component
sickn33
Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships. Creates component diagrams and documentation. Use when synthesizing code-level documentation into logical components.
agent-pseudocode
ruvnet
Agent skill for pseudocode - invoke with $agent-pseudocode
spec
matteocervelli
>
cs-arch
wildlily1021
维护 `codestable/architecture/` 这份只记现状的系统地图，三种模式 update / check / backfill。触发：用户说"刷新 architecture"、"做架构检查"、"补这个模块的架构文档"、"方案和代码对得上吗"，或 feature 阶段需要先做架构动作。不写未来规划（走 cs-roadmap）。