sdd-spec

Create Given/When/Then technical specifications in markdown for AI projects.

Updated May 9, 2026

Search Tags:#specification #spec writing #technical documentation #project requirements #Given/When/Then

Ready to run

npx skills add https://github.com/LeandroBenjaminL/lend-ai --skill sdd-spec-leandrobenjaminl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/LeandroBenjaminL/lend-ai/tree/main/skills/sdd-spec
Command: npx skills add https://github.com/LeandroBenjaminL/lend-ai --skill sdd-spec-leandrobenjaminl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you write comprehensive technical specifications (specs) for your AI projects, ensuring clarity and alignment in project requirements.

Core Features & Use Cases

Technical Spec Writing: Guides you through creating Given/When/Then specifications in markdown.
Spec Proposal Review: Triggered after a spec proposal is approved, helping to refine and expand on specifications.
Use Case: Use this Skill to draft specs for a new feature in your AI application, ensuring that all stakeholders have a clear understanding of the desired outcome.

Quick Start

After a feature proposal is approved, use the sdd-spec skill to create a technical spec document for the proposed feature.

Frequently Asked Questions about sdd-spec

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

FAQPage Schema

How do I write technical specifications for AI projects using Given/When/Then format?▼

To write technical specifications for AI projects, use a guided process to structure requirements into Given/When/Then markdown formats. This ensures project requirements are clearly defined, testable, and aligned across stakeholders before development begins.

What is the Given/When/Then format for technical spec writing?▼

The Given/When/Then format is a structured specification writing method that defines project requirements by stating the initial context, the action taken, and the expected outcome. It ensures technical specs remain clear and testable.

When do I need to create technical specs for project requirements?▼

You need to create technical specs for project requirements immediately after a feature proposal is approved. Drafting specifications at this stage ensures all stakeholders share a clear understanding of the desired AI project outcome before implementation.

Do I need prior project management knowledge to write technical specs with this approach?▼

Yes, writing technical specs with this approach requires existing knowledge of spec writing and project management principles. It is designed to guide and refine your specifications, rather than teach the foundational principles from scratch.

What is the best way to refine an approved spec proposal into a full technical document?▼

The best way to refine an approved spec proposal is to trigger a guided expansion process that fleshes out the Given/When/Then markdown structure. This systematically expands the initial proposal into comprehensive, testable project requirements.

Why use Given/When/Then markdown for AI project requirements instead of standard documentation?▼

Using Given/When/Then markdown for AI project requirements enforces testable conditions and clear alignment. Unlike standard documentation, this structured format explicitly maps contexts and actions to expected outcomes, reducing ambiguity for stakeholders.