
Clavix Refine
Refine PRDs and prompts through guided iteration with change tracking
What You Can Do
You can load existing PRDs or saved prompts, discuss targeted improvements with Claude, and refine requirements without losing track of what changed. The skill manages source discovery, guides you through iteration cycles, and maintains clear modification markers ([ADDED], [MODIFIED], [REMOVED], [UNCHANGED]) so you always know what evolved during refinement.
Features
Automatically locates your existing PRDs and prompts from .clavix directories
Asks what you want to refine (PRD vs prompt) before making changes
Reads your current draft completely before suggesting modifications
Marks every update with [ADDED], [MODIFIED], [REMOVED], [UNCHANGED] labels
Structures refinement as discussion-based improvement cycles
Detects 6 common mistakes and redirects you back to refinement mode
Ensures existing requirements aren't accidentally removed without your approval
Confirms refinement mode is active and prevents implementation drift
Example Output
CLAVIX MODE: Refinement Mode: planning Purpose: Updating existing PRD Implementation: BLOCKED - I'll update requirements, not build them
Current PRD Found: mini-prd.md (1,247 words)
What would you like to refine?
- Add missing user personas
- Clarify acceptance criteria
- Update success metrics
- Expand technical constraints
Refinement Summary:
- [ADDED] Three new acceptance criteria for payment flow
- [MODIFIED] Success metric from "95% uptime" to "99.5% uptime during business hours"
- [UNCHANGED] User personas (4 total)
- [REMOVED] Legacy API compatibility requirement (per your request)
Updated PRD saved → .clavix/outputs/prd-refined-2024-01-15.md
What's Included
- SKILL.md instruction file with self-correction protocol and refinement workflow:
- Source discovery template mapping common PRD and prompt file locations:
- Modification tracking checklist ([ADDED], [MODIFIED], [REMOVED], [UNCHANGED] markers):
- State assertion format to confirm refinement mode before starting:
- Self-detection guide for 6 common refinement mistakes with correction steps:
Who It's For
- Product managers — refining PRDs through stakeholder feedback and iteration
- Business analysts — enhancing requirements documents with clarifications and scope adjustments
- Operations leaders — improving process documentation and system specifications
- Prompt engineers — iterating on saved prompts to improve consistency and output quality
- Project leads — tracking requirements evolution across refinement cycles
Best For
- Revising existing PRDs with new constraints or acceptance criteria
- Clarifying ambiguous requirements without starting from scratch
- Integrating stakeholder feedback into documented specifications
- Updating saved prompts based on Claude feedback and performance
- Maintaining audit trails of requirement changes across iterations
- Removing outdated or deprecated requirements with clear tracking







