dot-ai-prd-done

Orchestrate PRD implementation workflows with branch management, pull requests, reviews, merges, and issue closure.

2|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/vfarcic/dot-ai-website --skill dot-ai-prd-done
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dot-ai-prd-done
Source: https://github.com/vfarcic/dot-ai-website/tree/main/.claude/skills/dot-ai-prd-done
Command: npx skills add https://github.com/vfarcic/dot-ai-website --skill dot-ai-prd-done

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the entire process of completing a Product Requirements Document (PRD) implementation, from initial setup to final closure, ensuring consistency and efficiency.

Core Features & Use Cases

  • Automated Branching and Committing: Creates feature branches and manages commits based on PRD requirements.
  • Intelligent Pull Request Creation: Analyzes changes, auto-fills PR details, and prompts for missing information based on PR templates.
  • Review and Merge Orchestration: Guides the user through the review process, ensuring all checks pass before merging.
  • Issue Closure and Cleanup: Closes associated GitHub issues and cleans up local branches.
  • Use Case: A developer finishes implementing a new feature described in a PRD. They invoke this Skill to automatically create a Git branch, commit their code, generate a detailed pull request with all necessary information, get it reviewed, merge it, and close the corresponding issue.

Quick Start

Use the dot-ai-prd-done skill to complete the implementation for PRD issue 123.

Frequently Asked Questions about dot-ai-prd-done

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

FAQPage Schema
How do I automate pull request creation from a PRD implementation?

Automating pull request creation from a PRD involves analyzing committed changes and auto-filling PR details based on repository templates. This Skill orchestrates that workflow by generating branches, prompting for missing PR information, and guiding the review process.

What is the best way to manage GitHub issue closure after merging a feature branch?

Managing GitHub issue closure after a merge requires linking the pull request to the corresponding issue and verifying all checks pass. This Skill orchestrates the review, merge, and automated issue closure while cleaning up local branches.

How do I handle branch management and committing for a new feature workflow?

Branch management for a new feature workflow requires creating a dedicated feature branch and organizing commits based on requirements. This Skill automates the branching and committing process to ensure consistency before opening a pull request.

Can I use this workflow automation for documentation-only pull requests?

Yes, this workflow automation supports documentation-only completion scenarios. It orchestrates the end-to-end PRD workflow, including template analysis and pull request creation, ensuring documentation updates follow the same review and merge process.

Does the pull request template analysis prompt for missing information automatically?

Yes, pull request template analysis automatically identifies missing information during PR creation. The Skill evaluates changes against the PR template and actively prompts the user to supply any required details that were not auto-filled.

Why should I use an orchestrated workflow for PRD implementation instead of manual git commands?

An orchestrated PRD implementation workflow ensures consistency across branching, committing, and pull request creation. Unlike manual git commands, it automatically analyzes PR templates, guides the review process, and handles issue closure to prevent incomplete merges.