prd-taskmaster

Generate a PRD and publish it as a GitHub issue, then trigger the Shape-Spec workflow.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/bzellman/earp-kit --skill prd-taskmaster-bzellman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-taskmaster
Source: https://github.com/bzellman/earp-kit/tree/main/skills/system/prd-taskmaster
Command: npx skills add https://github.com/bzellman/earp-kit --skill prd-taskmaster-bzellman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

PRD Taskmaster provides a rigorous, auditable bridge from product ideas to executable engineering plans. It ensures a single source of truth by publishing PRDs as GitHub issues and coordinating downstream orchestration via Shape-Spec, reducing coordination overhead and ensuring consistent delivery.

Core Features & Use Cases

  • Publish a complete PRD as a GitHub issue to serve as the single source of truth for teams.
  • Automatically trigger /agent-os:shape-spec for scope-aware execution and quality gates.
  • Enforce no-deferral discipline by treating every requirement as must-deliver and surfacing automated validation checks.
  • Facilitate reuse and traceability of templates, patterns, and handoff workflows across projects.

Quick Start

Provide a feature request or PRD topic and the skill will generate a PRD, publish it as a GitHub issue, and trigger the Shape-Spec workflow.

Frequently Asked Questions about prd-taskmaster

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

FAQPage Schema
How do I publish a product requirements document as a GitHub issue for feature planning?

To publish a product requirements document (PRD) as a GitHub issue, provide a feature request or PRD topic. The system generates a comprehensive PRD and publishes it directly to GitHub issues to serve as a single source of truth for engineering teams.

What's the best way to turn PRDs into executable engineering plans automatically?

Turning PRDs into executable engineering plans is achieved by publishing the PRD as a GitHub issue and automatically triggering the Shape-Spec workflow. This coordinates scope-aware execution, applies quality gates, and enforces no-deferral discipline for consistent delivery.

Does the Shape-Spec workflow support automated validation checks for feature scope?

The Shape-Spec workflow supports automated validation by enforcing no-deferral rules that treat every requirement as must-deliver. It performs a final validation via the pr-handoff-to-codex process to surface automated checks before engineering handoff.

Can I use this PRD orchestration tool for coordinating downstream engineering tasks?

You can use this PRD orchestration tool for downstream coordination because it bridges product ideas to executable plans. After generating and publishing the PRD, it coordinates activation of the Shape-Spec workflow for scope-aware execution and quality gates.

Why does my feature planning need a no-deferral rule for product requirements?

A no-deferral rule is needed for feature planning because it treats every requirement as must-deliver, preventing scope creep. This discipline ensures rigorous, auditable delivery by surfacing automated validation checks before the final engineering handoff.

What is a PRD Taskmaster and how does it handle feature requests?

PRD Taskmaster is an orchestration tool that handles feature requests by generating a comprehensive PRD, publishing it as a GitHub issue, and coordinating downstream execution via the Shape-Spec workflow to reduce coordination overhead and ensure consistent delivery.