idea-to-pdd-qa

Validate PDD structure against 11 sections and archetype enums.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill idea-to-pdd-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idea-to-pdd-qa
Source: https://github.com/dimagi-internal/ace/tree/main/skills/idea-to-pdd-qa
Command: npx skills add https://github.com/dimagi-internal/ace --skill idea-to-pdd-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of incomplete or malformed Product Design Document (PDD) artifacts produced by the idea-to-pdd skill, which would otherwise block downstream quality evaluation, waste development time, and delay Connect opportunity deployment.

Core Features & Use Cases

  • 6 Static Structural Checks: Validates all 11 required PDD sections, correct archetype declarations, presence of stress test appendix, populated success metrics tables, layered evidence model references, and reviewer comment disposition tables when applicable.
  • Fast, Deterministic Validation: All checks run in under 100ms with no large language model required, making it lightweight for automated workflows and CI/CD pipelines.
  • Use Case: When a design team generates a new PDD for a Connect opportunity via the idea-to-pdd skill, this QA skill automatically runs first to catch structural errors like missing sections or invalid archetype values, preventing invalid PDDS from moving to quality evaluation.

Quick Start

Use the idea-to-pdd-qa skill to run structural validation on the PDD artifact generated for your current Connect opportunity and return a binary pass/fail verdict with auto-fix hints for any failures.

Frequently Asked Questions about idea-to-pdd-qa

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

FAQPage Schema
How do I validate a Product Design Document before downstream evaluation?

You can validate a Product Design Document by running structural QA checks that verify all required sections, correct archetype declarations, and necessary appendices are present before the document enters downstream evaluation.

What structural checks are required for PDD validation in the ACE lifecycle?

PDD validation in the ACE lifecycle requires six static checks covering 11 required sections, valid archetype enum values, stress test appendix presence, populated success metrics tables, layered evidence model references, and reviewer comment disposition tables.

Can I run static checks on a PDD without using a large language model?

Yes, you can run deterministic static checks on a PDD without a large language model. These structural validations execute in under 100ms, making them lightweight enough for automated workflows and CI/CD pipelines.

How do I catch missing sections and malformed declarations in a generated PDD?

To catch missing sections and malformed declarations in a generated PDD, apply binary structural quality assurance that returns a pass/fail verdict with auto-fix hints, enabling automated remediation of the detected errors.

Does PDD structural validation return auto-fix hints for failed checks?

Yes, PDD structural validation returns structured QA results with auto-fix hints for failed checks. This enables automated remediation of formatting errors, missing sections, and invalid archetype values.

When should I use a quality gate for product design documents?

You should use a quality gate for product design documents when a design team generates a new PDD for a Connect opportunity, ensuring invalid artifacts are caught before they block quality evaluation or delay deployment.