prd-v06-technical-specification

Generate API endpoint contracts and data model definitions from PRD architectural decisions.

193|9|Updated Jul 10, 2025
One-click install
npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill prd-v06-technical-specification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-v06-technical-specification
Source: https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v06-technical-specification
Command: npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill prd-v06-technical-specification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Architects and product teams struggle to keep API surface and data models aligned with evolving architecture decisions across PRD cycles, leading to inconsistent interfaces and integration gaps.

Core Features & Use Cases

  • Generate API contracts (API-) and data model definitions (DBT-) from ARC-, TECH-, UJ-, SCR- decisions.
  • Validate cross-cutting consistency between endpoints and models, and produce ready-to-implement contracts for engineers.
  • Use cases include guiding v0.6/v0.7 build planning, documenting interfaces, and enabling downstream code generation.

Quick Start

Provide input of ARC decisions, TECH-build items, UJ flows, and SCR requirements to generate API- and DBT- ready contracts.

Frequently Asked Questions about prd-v06-technical-specification

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

FAQPage Schema
How do I generate API contracts from architectural decisions?

You can generate API endpoint contracts from PRD-driven architectural decisions by inputting ARC, TECH, UJ, and SCR items to produce ready-to-implement API definitions. The Skill enforces API output templates and cross-references SCR/UJ mappings for traceable entries.

How do I keep data models aligned with evolving API specifications across build cycles?

Keeping data models aligned with API specifications across build cycles requires validating cross-cutting consistency between endpoints and models. This Skill produces DBT definitions from architectural decisions to prevent inconsistent interfaces and integration gaps during v0.6 build planning.

What is the best way to define database schemas from user journey requirements?

Defining database schemas from user journey requirements involves translating UJ flows and SCR requirements into structured data model definitions. The Skill generates DBT outputs that cross-reference architectural decisions, enabling traceable schemas and downstream code generation.

Do I need PRD v0.6 artifacts to plan my API surface and endpoint architecture?

Yes, planning your API surface requires PRD v0.6 artifacts like ARC decisions and TECH-build items as input. The Skill uses these specific architectural inputs to enforce API output templates and generate ready-to-implement endpoint contracts for engineers.

Can I use these API contracts for downstream code generation and build planning?

Yes, the generated API contracts and data model definitions are designed to enable downstream code generation and guide v0.6 build planning. The outputs enforce structured templates that document interfaces for direct implementation by engineering teams.