design-science-methodology skillA
design-science-methodology is agent-read markdown (skill) from khaledsaeed18/dotclaude: Structure a thesis whose contribution is a built artifact (tool, system, method, model) using design science research: explicit problem and requirements, knowledge base, iterative build with design decisions recorded, and a rigorous evaluation strategy (technical benchmarks, controlled use, case study, expert review) that separates whether it works from whether it helps, following Hevner's guidelines and Peffers' process. Use when the thesis builds something, when a supervisor says a system alon.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
Building a system is engineering; showing what is learned from building it is research. Design science research (DSR) is the frame that turns the first into the second: an artifact designed to solve a stated problem, evaluated with rigour, and a contribution to knowledge stated separately from the artifact itself. ## The process (Peffers et al.) 1. **Problem identification and motivation**: the problem, who has it, why existing solutions fall short (from `lit-review-synthesis`), and why solving it matters. Concrete and, where possible, quantified. 2. **Objectives of the solution**: requirements the artifact must meet, derived from the problem and the literature. Functional (must do X) and quality (latency under Y, usable by Z without training). Each requirement is later a row in the evaluation table. Number them (R1..Rn). 3. **Design and development**: the artifact, with its design decisions recorded as they are made (`adr-writing` works for this) and the knowledge they draw on (which theories, patterns, prior systems). The thesis describes architecture and the decisions, not every line. …
Read the whole file at its exact version.
How to install
mdr add khaledsaeed18/dotclaude/design-science-methodology@git:20260921.c8f5dc3mdr add khaledsaeed18/dotclaude/design-science-methodology@sha256:e043d827e9505846Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_da4wmrz3yy6knvl3)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5278 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
khaledsaeed18/dotclaude · 5 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_da4wmrz3yy6knvl3 GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/design-science-methodology GET https://markdownregistry.com/api/v1/blob/e043d827e9505846935f24045becd3bb738faf3441c7c3affb8abfca1f76b730
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.