skillgrid-prd-artifacts

Manage PRD creation, numbering, status, and OpenSpec alignment.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/devopstales/aiskillgrid --skill skillgrid-prd-artifacts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skillgrid-prd-artifacts
Source: https://github.com/devopstales/aiskillgrid/tree/main/.agents/skills/skillgrid-prd-artifacts
Command: npx skills add https://github.com/devopstales/aiskillgrid --skill skillgrid-prd-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill simplifies the management of Product Requirements Documents (PRDs), their numbering, status fields, and linking to OpenSpec changes, streamlining the PRD lifecycle and ensuring alignment with technical specifications.

Core Features & Use Cases

  • PRD Artifact Management: Handles the creation, updating, and renumbering of PRDs.
  • OpenSpec Alignment: Ensures PRDs are aligned with corresponding OpenSpec changes.
  • Status Tracking: Monitors the status of PRDs throughout their lifecycle.
  • Use Case: When creating or updating a PRD, use this skill to manage its lifecycle, numbering, and linking to the appropriate OpenSpec change.

Quick Start

Trigger the skill with a command like /skillgrid-prd-artifacts create <PRD title> to create a new PRD.

Frequently Asked Questions about skillgrid-prd-artifacts

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

FAQPage Schema
How do I manage Product Requirements Documents and keep them aligned with OpenSpec changes?

PRD management involves creating, updating, and renumbering documents while maintaining alignment with OpenSpec changes through file naming conventions and indexing to ensure specification consistency throughout the lifecycle.

What is the best way to track PRD status fields throughout the document lifecycle?

PRD status tracking monitors document lifecycle stages by maintaining status fields and indexing, ensuring product documentation remains organized and aligned with corresponding OpenSpec modifications.

How do I create and renumber PRDs using file naming conventions?

Creating and renumbering PRDs requires applying structured file naming conventions and indexing, allowing you to generate new documents, update existing artifacts, and maintain numerical order across the product documentation.

Can I split and link existing Product Requirements Documents to OpenSpec changes?

Splitting and linking PRDs to OpenSpec changes is supported natively, allowing you to divide existing product documentation and establish direct links to corresponding technical specification modifications during updates.

When do I need to renumber PRDs and update their OpenSpec alignment?

Renumbering PRDs and updating OpenSpec alignment is necessary when splitting documents, creating new artifacts, or modifying product requirements, ensuring file indexing and status fields remain consistent with specification changes.