One-click install
npx skills add https://github.com/g5becks/oxlint-plugins --skill clavix-prd-g5becks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clavix-prd
Source: https://github.com/g5becks/oxlint-plugins/tree/main/.skills/clavix-prd
Command: npx skills add https://github.com/g5becks/oxlint-plugins --skill clavix-prd-g5becks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of comprehensive Product Requirements Documents (PRDs) by guiding users through a structured, strategic questioning process, ensuring all critical aspects of a new feature or project are defined before development begins.

Core Features & Use Cases

  • Strategic Questioning: Asks targeted questions one at a time to elicit detailed requirements.
  • PRD Generation: Creates both a full PRD and an AI-optimized quick reference version.
  • Quality Assurance: Validates PRD completeness and clarity for AI consumption.
  • Use Case: When planning a new mobile app feature, use this Skill to define the problem, core features, technical constraints, and out-of-scope items, resulting in a clear PRD for the development team.

Quick Start

Use the clavix-prd skill to start defining requirements for a new user authentication system.

Frequently Asked Questions about clavix-prd

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

FAQPage Schema
How do I write a product requirements document for a new feature?

To write a product requirements document, you need to define the problem statement, core features, technical constraints, and out-of-scope items. This Skill guides you through a structured questioning process to capture these details and generates a clear PRD for your development team.

What is a quick-reference PRD and why do I need one?

A quick-reference PRD is an AI-optimized version of your full product requirements document. It ensures the requirements are structured clearly for both human consumption and AI processing, validating completeness and clarity for downstream technical use.

Can I use this to plan technical requirements for a mobile app feature?

Yes, you can use this Skill to plan technical requirements for a mobile app feature. It facilitates detailed project planning by guiding you through targeted questions to clarify scope, constraints, and core features before development begins.

What's the best way to gather requirements for product strategy documentation?

The best way to gather requirements for product strategy documentation is through strategic questioning. This Skill asks targeted questions one at a time to elicit detailed requirements, ensuring all critical aspects of your project are defined comprehensively.

How do I define scope exclusions in a PRD?

To define scope exclusions in a PRD, you must explicitly identify out-of-scope items during the requirements gathering process. This Skill prompts you to clarify these boundaries, preventing scope creep and aligning development team expectations.