generate-strategic-charter-and-prd

Generate strategic charters and PRDs from VOC, KTLO, and truth-based evidence.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/nuggetswise/pmos --skill generate-strategic-charter-and-prd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-strategic-charter-and-prd
Source: https://github.com/nuggetswise/pmos/tree/main/skills/generate-strategic-charter-and-prd
Command: npx skills add https://github.com/nuggetswise/pmos --skill generate-strategic-charter-and-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables product teams to generate strategic charters and PRDs from VOC, KTLO, and truth-based evidence, turning inputs into actionable bets and requirements.

Core Features & Use Cases

  • Charter generation: Produce 3-5 strategic bets with strategic reasoning and clear problem statements.
  • PRD drafting: Convert selected charter into engineering requirements with scope, constraints, and acceptance criteria.
  • Audience-specific formats: exec, eng, full; supports /charters and /prd formats.
  • Evidence-driven: All outputs cite sources and map to truth_base, VOC, KTLO to ensure traceability.

Quick Start

Use the /charters command to generate quarterly charters from VOC and KTLO inputs, or use /prd to create detailed PRDs. Ensure inputs exist in truth_base, VOC, and KTLO directories; outputs will be written to outputs/roadmap and outputs/delivery/prds.

Frequently Asked Questions about generate-strategic-charter-and-prd

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

FAQPage Schema
How do I generate a strategic product charter from VOC and KTLO inputs?▼

To generate a strategic product charter from VOC and KTLO inputs, use the /charters command to process evidence sources and produce 3-5 actionable strategic bets with clear problem statements and strategic reasoning.

How does evidence citation work when creating a PRD from a strategic charter?▼

Evidence citation works by mapping all PRD requirements and charter reasoning directly to truth_base, VOC, and KTLO sources, ensuring full traceability for engineering scoping and audience-specific formats.

What's the best way to convert a selected charter into engineering requirements?▼

The best way to convert a selected charter into engineering requirements is using the /prd command, which drafts detailed PRDs with scope, constraints, and acceptance criteria mapped to your evidence base.

Do I need a truth_base directory to create product charters and PRDs?▼

Yes, inputs must exist in the truth_base, VOC, and KTLO directories before execution. The skill reads these evidence sources to generate charters and writes outputs to outputs/roadmap and outputs/delivery/prds.

Can I tailor PRD outputs for different audiences like engineering and executives?▼

Yes, you can tailor PRD outputs for different audiences. The skill supports exec, eng, and full formats, allowing you to generate audience-specific documents from the same evidence base.