dapp-sdd:specify

Generate a structured specification document from a dApp README.

Updated Feb 5, 2026

Search Tags:#template #specification #readme #dapp #user-stories #acceptance-criteria

Ready to run

npx skills add https://github.com/aaronbassett/midnight-knowledgebase --skill dapp-sdd-specify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dapp-sdd:specify
Source: https://github.com/aaronbassett/midnight-knowledgebase/tree/main/plugins/dapp-sdd/skills/specify
Command: npx skills add https://github.com/aaronbassett/midnight-knowledgebase --skill dapp-sdd-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams turn a README-based description of a dApp into a formal, testable specification that can be used for planning and validation.

Core Features & Use Cases

Automates extraction of the core concept from a README and structures it into a specification with an overview, user stories, technical requirements, and scope.
Supports 2-4 user stories with clear acceptance criteria and mapping to a compact contract design.
Provides a reusable template that can be saved as .dapp-sdd/spec.md for future dApps.

Quick Start

Read the README.md content for the dApp and run the specification generator to produce the .dapp-sdd/spec.md.

Frequently Asked Questions about dapp-sdd:specify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a specification from a README for a dApp?▼

You can generate a specification by running a specification generator on your README.md content. It automatically extracts the core concept and structures it into a formal spec with an overview, user stories, technical requirements, and out-of-scope notes, saving the result as spec.md.

What is a README-driven specification for decentralized applications?▼

A README-driven specification is a formal, testable document derived from a dApp's README. It translates high-level concepts into structured technical requirements and user stories with acceptance criteria, enabling proper project planning and validation before development begins.

Can I map user stories to smart contract designs automatically?▼

Yes, generating a specification from your README can map 2-4 user stories with clear acceptance criteria to a compact contract design. This ensures your dApp's technical requirements align directly with user expectations and defined scope boundaries.

Does the specification template support acceptance criteria and out-of-scope notes?▼

Yes, the specification template explicitly includes sections for user stories with acceptance criteria and an Out of Scope section. It delivers a structured specification document outlining technical requirements and project boundaries, saving directly to spec.md.

What is the best way to structure technical requirements for a dApp?▼

The best way to structure technical requirements is by expanding README descriptions into a complete specification document. This organizes requirements alongside an overview, user stories, and out-of-scope notes, providing a comprehensive blueprint for dApp development and testing.

Why do I need a formal spec when my dApp already has a README?▼

You need a formal spec because a README typically lacks testable acceptance criteria and structured technical requirements. Converting it into a specification provides a formalized document for validation and planning, ensuring development aligns with defined user stories and project boundaries.