Create Given/When/Then technical specifications in markdown for AI projects.
npx skills add https://github.com/LeandroBenjaminL/lend-ai --skill sdd-spec-leandrobenjaminl
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
This Skill helps you write comprehensive technical specifications (specs) for your AI projects, ensuring clarity and alignment in project requirements.
After a feature proposal is approved, use the sdd-spec skill to create a technical spec document for the proposed feature.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
thiagoooo34252Create technical design documents in markdown from proposal and specification documents.
Z1-TestCreate executable behavior specifications using Gherkin Given/When/Then syntax.
runchr-comGenerate a stakeholder map and communication plan for a project.
TabTabGoGenerate structured business requirement documents in Word (.docx) format.
