Generate and organize versioned PRD documents across docs/prd directories.
npx skills add https://github.com/kociii/prd-manager --skill prd-manager-kociii
Please help me install this Agent Skill. Skill: prd-manager Source: https://github.com/kociii/prd-manager/tree/main Command: npx skills add https://github.com/kociii/prd-manager --skill prd-manager-kociii
This Skill provides a centralized, automated workflow to organize and generate versioned PRD documentation under docs/prd/<version>/, ensuring consistency and repeatable governance across product lifecycles.
Create a new PRD version to start the full documentation workflow.
High-intent search queries and answers about installing and using this skill.
To organize versioned PRD documents, this Skill automates the creation and generation of structured markdown files across docs/prd/<version>/ directories. It initializes version folders from templates and enforces clear documentation boundaries for consistent product lifecycle tracking.
Available product requirement documentation templates include prd.md, design.md, plan.md, and dev.md. These templates enforce documentation boundaries and enable clean handoffs between product requirements, design, planning, and development phases.
Yes, you can compare changes and archive outdated PRD versions across frontend and backend projects. The Skill manages existing PRD versions by allowing you to view, extend, search across versions, and archive old releases to maintain a clear version history.
The best way to automate project management documentation is by generating new PRD version folders from predefined templates. This workflow centralizes version control, initializes required directories, and produces structured outputs including optional SQL assets for clean handoffs.
Yes, this PRD versioning workflow supports both frontend and backend project separation. It handles creating new versions from templates, updating and comparing documents, and archiving old versions specifically across frontend and backend project directories.
Enforcing documentation boundaries in versioned PRD folders ensures consistency and repeatable governance across product lifecycles. It separates product requirements, design, planning, and development outputs into distinct markdown files for clean team handoffs.
asermaxInitialize katachi framework directories and CLAUDE.md baseline in projects.
k1064190Convert YAML trading signal tickets into structured edge concepts with thesis and invalidation logic.
forwardimpactConvert Markdown to HTML and generate static documentation sites.
fkguoAutomate Markdown quality checks for formatting and rendering issues.
