prd-workflow

Automate PRD-driven feature delivery across claim, build, ship, and cleanup phases.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/mdmagnuson-creator/yo-go --skill prd-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-workflow
Source: https://github.com/mdmagnuson-creator/yo-go/tree/main/skills/prd-workflow
Command: npx skills add https://github.com/mdmagnuson-creator/yo-go --skill prd-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable workflow to move features from PRDs into shipped software, coordinating four phases (claim, build, ship, cleanup) with guardrails, checks, and automation triggers.

Core Features & Use Cases

  • PRD-to-track workflow: Automates progression of features from PRD draft to ready-to-ship.
  • Phase orchestration: Coordinates Claim, Build, Ship, and Cleanup with mandatory quality gates.
  • Risk and guardrails: Enforces git commit discipline, credential readiness, and architecture checks before shipping.

Quick Start

Start by selecting a PRD to implement and follow the four phases to drive development, testing, and release.

Frequently Asked Questions about prd-workflow

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

FAQPage Schema
How do I automate PRD-driven feature delivery from start to finish?

PRD-driven feature delivery is automated by orchestrating claim, build, ship, and cleanup phases with mandatory quality gates. This workflow moves features from PRD draft to ready-to-ship while enforcing guardrails and triggering automation.

How does phase orchestration work for product management workflows?

Phase orchestration coordinates four stages—claim, build, ship, and cleanup—ensuring mandatory quality checks are satisfied before progression. It enforces git commit discipline, credential readiness, and architecture validation to move features safely toward release.

What quality checks are required before shipping a feature in a PRD workflow?

Shipping a feature requires satisfying guardrails including git commit discipline, credential readiness, architecture validation, and E2E testing automation. These checks are mandatory quality gates enforced before transitioning to the ship phase.

Can I enforce git commit discipline and architecture validation during feature development?

Yes, the workflow enforces git commit discipline and architecture validation as mandatory guardrails during the build and ship phases. These checks ensure code quality and structural integrity before features are released.

Do I need existing CI-CD pipelines to use a PRD-to-track workflow?

The workflow triggers E2E testing automation and coordinates shipping, but the metadata does not specify a dependency on existing CI-CD pipelines. It enforces git commit discipline and architecture validation as built-in quality gates.

What is the best way to manage feature progression from PRD draft to release?

Managing feature progression is best handled by following a structured four-phase workflow: claim, build, ship, and cleanup. This approach enforces risk guardrails and quality checks to ensure a repeatable path from PRD to shipped software.