From dude
Document specifications using the dude MCP server. List, create, update specifications. Record requirements, architecture decisions, API contracts, design patterns. Search for specs. Use when documenting requirements, recording architecture decisions, writing API specs, capturing design patterns, or managing technical documentation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dude:specificationsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Document requirements and architecture via the `dude:` MCP tools.
Document requirements and architecture via the dude: MCP tools.
Specs and architecture decisions are stored as records with kind "spec" or "arch".
dude:list_records { "kind": "spec" } - List specifications
dude:list_records { "kind": "arch" } - List architecture decisions
dude:upsert_record { "kind": "spec", "title": "API: POST /users ..." } - Create spec
dude:search { "query": "...", "kind": "spec" } - Find specs
dude:list_records { "kind": "spec" }
dude:list_records { "kind": "arch" }
dude:list_records { "kind": "spec", "status": "open" }
Parameters:
kind — "spec" for specifications, "arch" for architecture decisionsstatus (optional) — "open", "resolved", "archived", or "all"project (optional) — project name, or "*" for all projectsdude:get_record { "id": 42 }
Parameters:
id (required): Record ID (integer)dude:upsert_record {
"kind": "spec",
"title": "AUTH: JWT tokens with 24h expiry",
"body": "Refresh handled in authMiddleware.js. Tokens are RS256 signed."
}
dude:upsert_record {
"kind": "arch",
"title": "ARCH: Use libsql for local+cloud hybrid storage",
"body": "Local SQLite file with optional Turso cloud sync."
}
Parameters:
kind (required): "spec" or "arch"title (required): Short summary (use prefixes below)body (optional): Full descriptionstatus (optional): Defaults to "open"Provide the id of an existing record to update it:
dude:upsert_record {
"id": 42,
"kind": "spec",
"title": "AUTH: JWT tokens with 1h expiry (changed from 24h)",
"body": "Updated based on security review..."
}
Set status to "archived" to mark as deprecated:
dude:upsert_record { "id": 42, "kind": "spec", "title": "...", "status": "archived" }
dude:delete_record { "id": 42 }
dude:search {
"query": "authentication flow JWT tokens",
"kind": "spec",
"project": "my-org/my-repo",
"limit": 10
}
Parameters:
query (required): Natural language search querykind (optional): "spec" or "arch" to filter resultsproject (optional): Project name to boost, or "*" for equal weightlimit (optional): Max results (default 5)Use prefixes to categorize:
AUTH: - Authentication/authorizationAPI: - API contractsARCH: - Architecture decisionsDATA: - Data models/schemasUI: - User interface patternsnpx claudepluginhub fingerskier/claude-plugins --plugin dudeLoads ADR and spec context for architecture-aware responses. Use when starting a new session or referencing existing decisions. Supports cross-module aggregation and qmd-based freshness checks.
Provides conventions for writing self-contained, implementation-ready spec documents. Distinguishes specs from docs; covers structure including data model, architecture, security, operations, scope, and deliverables.
Transforms ideas into structured specifications (requirements, design, tasks) before implementation. Use when building features, fixing bugs, refactoring, or designing systems.