clavix-refine

Refine existing PRDs and prompts with change markers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you improve and update existing Product Requirement Documents (PRDs) or saved prompts, rather than starting from scratch.

Core Features & Use Cases

  • Iterative Improvement: Enhance current drafts of PRDs or prompts based on new feedback or requirements.
  • Content Awareness: Loads existing content before suggesting changes, ensuring context is maintained.
  • Change Tracking: Clearly marks additions, modifications, and removals for easy review.
  • Use Case: You have a draft PRD for a new feature, but stakeholders have provided feedback. Use this Skill to incorporate that feedback directly into the existing PRD, updating requirements and scope without rewriting the entire document.

Quick Start

Use the clavix-refine skill to update the 'user-auth' PRD.

Frequently Asked Questions about clavix-refine

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

FAQPage Schema
How do I update an existing PRD with new stakeholder feedback without rewriting the whole document?

To update an existing PRD, load the current content and apply user-guided modifications iteratively. This refinement process integrates new feedback directly into the document, enhancing requirements while preserving the original scope.

What is the best way to track changes when iteratively refining prompts?

Tracking changes during prompt refinement uses specific markers like [ADDED], [MODIFIED], [REMOVED], and [UNCHANGED]. This clearly highlights additions, modifications, and removals for easy review of the updated content.

Can I use this approach to create a new Product Requirement Document from scratch?

No, you cannot use this refinement approach to create a new Product Requirement Document from scratch. It operates within defined mode boundaries, focusing strictly on enhancing and updating existing PRDs rather than new creation.

How do modifications to a saved prompt impact associated task files?

Modifications to a saved prompt can impact associated task files. The refinement process includes warnings about potential impacts, ensuring you are aware of downstream effects before finalizing content updates to your existing prompts.

Does this prompt refinement method load existing content before suggesting changes?

Yes, this prompt refinement method loads existing content before suggesting changes. This content awareness ensures context is maintained, allowing the iterative improvement process to enhance current drafts based on new requirements accurately.

What are the limitations of iteratively refining existing PRDs?

Limitations of iteratively refining existing PRDs include the inability to generate new documents from scratch and the necessity of managing potential impacts on associated task files when content updates or removals occur.