commit_prd

Merge draft PRD files into the official PRD folder with versioned archiving.

1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/KREUZc/InitialP --skill commit-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit_prd
Source: https://github.com/KREUZc/InitialP/tree/main/.agent/skills/commit_prd
Command: npx skills add https://github.com/KREUZc/InitialP --skill commit-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates draft PRD documents into the official PRD folder, while archiving history to preserve changes and enable traceability.

Core Features & Use Cases

  • Automated draft-to-PRD integration with versioned archiving and timestamped history.
  • Intelligent merging that preserves existing content while incorporating updates from drafts, with conflict detection and user prompts when needed.
  • Use Case: A product team drafts a feature spec in projectDoc/draftPRD; with this skill, the draft is merged into projectDoc/PRD, the original draft is archived, and a timestamped copy is created to track changes.

Quick Start

Provide the draft PRD file path and run the commit PRD action to merge it into the official PRD.

Frequently Asked Questions about commit_prd

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

FAQPage Schema
How do I merge draft PRD files into the official project documentation folder?

Merging a draft PRD into the official project documentation folder involves providing the draft file path; the skill then consolidates the draft into the official PRD directory while archiving the original and creating a timestamped history copy.

What is version-aware merging for product requirement documents?

Version-aware merging for product requirement documents is an intelligent process that preserves existing PRD content while incorporating updates from drafts, automatically detecting conflicts and prompting users for manual decisions when needed.

How does conflict detection work when updating product specs?

Conflict detection during product spec updates works by identifying inconsistencies between the existing official PRD and the new draft; when conflicts occur, the skill pauses automated merging and prompts the user for a manual resolution decision.

Can I use this to archive PRD history with timestamped copies?

Yes, you can use this to archive PRD history with timestamped copies. The skill automatically moves original draft files to an archive folder and generates timestamped versions to preserve changes and ensure full traceability of evolving feature specs.

Do I need any special dependencies to consolidate draft PRDs?

No, you do not need any special dependencies to consolidate draft PRDs. The skill operates independently without external components, requiring only the file path of your draft product requirement document to execute the automated merging and archiving workflow.

What is the best way to manage evolving PRDs for new feature drafts?

The best way to manage evolving PRDs for new feature drafts is using an automated draft-to-PRD integration workflow that handles file copying, smart merging, and versioned archiving, ensuring traceable updates without losing existing project documentation content.