sdd-expert

Convert PRDs into prioritized technical specifications with P0/P1/P2 architecture and agent-workflow specs.

Updated Feb 19, 2026

Search Tags:#architecture #documentation #specification #engineering #sdd #prd #ai-agent-workflow

Ready to run

npx skills add https://github.com/jonnathan-ls/ai-context-kit --skill sdd-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-expert
Source: https://github.com/jonnathan-ls/ai-context-kit/tree/main/skills/sdd-expert
Command: npx skills add https://github.com/jonnathan-ls/ai-context-kit --skill sdd-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridge the gap between business intent in PRDs and unambiguous technical specifications to guide engineering teams with a clear contract.

Core Features & Use Cases

Specification mapping: Convert PRDs into structured technical specs (architecture, API, or AI/agent workflow).
Specification prioritization: Generate a Specification Map with P0/P1/P2 priorities, focusing first on high-risk areas.
AI/Agent Workflow readiness: Produce prompts, memory models, tools, and recovery strategies for AI agents.

Quick Start

Provide your PRD or core idea so I can generate an initial Specification Map and identify the highest-risk spec to start detailing.

Frequently Asked Questions about sdd-expert

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

FAQPage Schema

How do I convert a PRD into technical specifications for engineering teams?▼

To convert a PRD into technical specifications, extract core engineering implications and map them into structured specs. Apply risk-based prioritization to deliver P0 architecture and agent-workflow specs first, followed by P1 and P2 items.

What is the best way to prioritize specifications from a product requirements document?▼

The best way to prioritize specifications from a PRD is generating a Specification Map using a risk-based approach. This targets high-risk areas first, categorizing technical requirements into P0, P1, and P2 priorities to guide engineering teams.

How do I define AI agent workflows and interfaces from a PRD?▼

To define AI agent workflows from a PRD, translate business intent into machine-readable templates. This process specifies data models, memory structures, prompts, tool interfaces, and success or failure criteria to ensure agent readiness.

Can I generate architecture and data models directly from business requirements?▼

Yes, generating architecture and data models directly from business requirements is possible. By identifying core engineering implications within the PRD, you produce concrete technical specifications and data models that serve as a clear contract for engineering teams.

What is included in a Specification Map for AI-agent workflows?▼

A Specification Map for AI-agent workflows includes risk-based P0, P1, and P2 prioritizations. It defines data models, prompts, tool interfaces, memory models, and recovery strategies within machine-readable and AI-friendly templates.

When do I need to translate a PRD into machine-readable templates?▼

Translating a PRD into machine-readable templates is needed when bridging the gap between business intent and unambiguous technical specifications. This defines data models and tool interfaces to guide engineering teams with a clear contract.