Dragon Dev Loop
Standard development process. No exceptions for any code change delivered to Dino.
The Loop
code
1. REQUIREMENTS (Balerion) → PRD / REQUIREMENTS.md 2. TESTS FIRST (Vermithrax 🛡️) → Test spec + acceptance criteria 3. IMPLEMENT (Caraxes 🔴) → Code against tests 4. QA (Vermithrax 🛡️) → Test, report, PASS/FAIL 5. FAIL? → Back to 3 → Loop until PASS 6. PASS → Deliver to Dino → With FULL protocol in chat
Roles
| Dragon | Role | When |
|---|---|---|
| Balerion | Requirements, orchestration, final validation, delivery | Start + End |
| Vermithrax 🛡️ | Define tests, QA report, PASS/FAIL | Before + After implementation |
| Caraxes 🔴 | Implement, fix findings | Middle |
Delivery Protocol (MANDATORY)
Every delivery to Dino includes IN THE CHAT:
- •Requirements document (path + key requirements)
- •Test specification (path + what/how tested)
- •Traceability matrix (requirement → test → result)
- •All file paths
- •Pass/fail decision with numbers
No "it's done, check it out"! Always full protocol.
Escalation
- •Loop > 3x without PASS → Report to Dino with analysis
- •Unclear requirements → Ask Dino BEFORE starting
- •Technically impossible → Report with alternatives
Rules
- •No code without requirements
- •No code without tests (Vermithrax defines tests BEFORE implementation)
- •No FAIL delivered to Dino — loop until PASS
- •Always full protocol on delivery
- •Vermithrax has final say on quality
- •Loop is mandatory — Balerion starts it automatically