Clavix — Prompts
Excerpt 1: clavix-prd — State Assertion (REQUIRED)
Source: src/templates/skills/prd.md
## State Assertion (REQUIRED)
**Before starting PRD development, output:**
CLAVIX MODE: PRD Development
Mode: planning
Purpose: Guiding strategic questions to create comprehensive PRD documents
Implementation: BLOCKED - I will develop requirements, not implement the feature
Technique: Mandatory mode banner. The AI must output a visible state declaration before any PRD work begins, making the current workflow phase explicit and blocking implementation. This is enforced by the skill description stating it is REQUIRED — there is no code check, just a strong instruction.
Excerpt 2: clavix-prd — Self-Correction Protocol
Source: src/templates/skills/prd.md
## Self-Correction Protocol
**DETECT**: If you find yourself doing any of these 6 mistake types:
| Type | What It Looks Like |
|------|--------------------|
| 1. Implementation Code | Writing function/class definitions, creating components, generating API endpoints, test files, database schemas |
| 2. Skipping Strategic Questions | Not asking about problem, users, features, constraints, or success metrics |
| 3. Incomplete PRD Structure | Missing sections: problem statement, user needs, requirements, constraints |
| 4. No Quick PRD | Not generating the AI-optimized 2-3 paragraph version alongside full PRD |
| 5. Missing Task Breakdown Offer | Not offering to generate tasks.md with actionable implementation tasks |
| 6. Capability Hallucination | Claiming features Clavix doesn't have, inventing workflows |
**STOP**: Immediately halt the incorrect action
**CORRECT**: Output:
"I apologize - I was [describe mistake]. Let me return to PRD development."
**RESUME**: Return to the PRD development workflow with strategic questioning.
Technique: Detect-Stop-Correct-Resume (DSCR) pattern. Unlike superpowers' Iron Law (prohibition statement + rationalization table), Clavix's Self-Correction Protocol is a fault-handling loop: detect the deviation type, halt, announce, resume. The 6-type enumeration is exhaustive and specific, reducing ambiguity about what counts as a violation.
Excerpt 3: PRD Question Flow — Validation Gates
Source: src/templates/prd-questions.md
## Question 1
**text:** 🎯 What are we building and why? (Problem + goal in 2-3 sentences)
**type:** text
**required:** true
**validation:** minLength:20
## Question 2
**text:** ⚡ What are the must-have core features? (List 3-5 critical features)
**type:** text
**required:** true
**validation:** minLength:30
## Question 4
**text:** 🚫 What is explicitly OUT of scope? (What are we NOT building?)
**type:** text
**required:** true
**validation:** minLength:15
Technique: Structured Q&A with validation constraints. Questions 1, 2, and 4 are required with minimum length validation, enforcing substantive answers before proceeding. Questions 3 and 5 are optional with skip instructions, reducing friction for teams with less context.