idea-to-pdd

Convert an initial idea into a complete Program Design Doc for a Connect application.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Idea-to-PDD Skill helps teams convert early briefs into a complete Program Design Doc (PDD) for a Connect application, reducing ambiguity and accelerating alignment with stakeholders.

Core Features & Use Cases

  • Draft PDD structure including Archetype, Problem Statement, Intervention Design, Learn App Specification, Deliver App Specification, Target Population, FLW Requirements, LLO Preference, Success Metrics, Evidence Model, and Timeline.
  • Automatically incorporate archetype-specific questions (atomic-visit, focus-group, multi-stage) and explicit stage gates to guide progress.
  • Gate-ready output in ACE/<opp-name>/pdd.md with a Stress Test appendix and a Gate Brief, enabling downstream skills and humans to proceed confidently.

Quick Start

Run /ace:step idea-to-pdd for your opp to generate a complete PDD draft from ACE/<opp-name>/idea.md.

Frequently Asked Questions about idea-to-pdd

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

FAQPage Schema
How do I convert an idea into a Program Design Doc for a Connect app?

To convert an idea into a Program Design Doc (PDD), provide your initial brief in ACE/<opp-name>/idea.md. The system generates a complete PDD draft with problem statements, app specifications, and success metrics to ACE/<opp-name>/pdd.md.

What should a Program Design Doc include for multi-stage Connect applications?

A Program Design Doc for multi-stage Connect applications should include archetype-specific questions, explicit stage-gate criteria, Learn and Deliver App specifications, target population, success metrics, and a timeline to guide program progress.

How do I structure stage-gate criteria in a program design document?

Structure stage-gate criteria in a program design document by applying archetype-specific logic for atomic-visit, focus-group, or multi-stage flows. The generated PDD includes a stress-test rubric appendix and a gate brief to validate readiness.

Can I generate a PDD from an idea file without manual formatting?

Yes, you can generate a PDD directly from an unformatted idea.md file. The system enforces a base PDD structure, automatically incorporating intervention design, FLW requirements, and LLO preferences without manual formatting.

Does the PDD generation process support Google Drive integration?

Yes, the PDD generation process supports Google Drive integration. It uses the Google Drive MCP to read your initial idea file and write the completed program design document directly back to your ACE directory.

Why are archetype-specific questions important in a program design doc?

Archetype-specific questions are important in a program design doc because they tailor the intervention logic to atomic-visit, focus-group, or multi-stage models. This ensures the Learn and Deliver app specifications match the target population's actual workflow.