Phillip Tarrant
df26abd207
Add YAML-driven quest system with context-aware offering:
Core Implementation:
- Quest data models (Quest, QuestObjective, QuestReward, QuestTriggers)
- QuestService for YAML loading and caching
- QuestEligibilityService with level, location, and probability filtering
- LoreService stub (MockLoreService) ready for Phase 6 Weaviate integration
Quest Content:
- 5 example quests across difficulty tiers (2 easy, 2 medium, 1 hard)
- Quest-centric design: quests define their NPC givers
- Location-based probability weights for natural quest offering
AI Integration:
- Quest offering section in npc_dialogue.j2 template
- Response parser extracts [QUEST_OFFER:quest_id] markers
- AI naturally weaves quest offers into NPC conversations
API Endpoints:
- POST /api/v1/quests/accept - Accept quest offer
- POST /api/v1/quests/decline - Decline quest offer
- POST /api/v1/quests/progress - Update objective progress
- POST /api/v1/quests/complete - Complete quest, claim rewards
- POST /api/v1/quests/abandon - Abandon active quest
- GET /api/v1/characters/{id}/quests - List character quests
- GET /api/v1/quests/{quest_id} - Get quest details
Frontend:
- Quest tracker sidebar with HTMX integration
- Quest offer modal for accept/decline flow
- Quest detail modal for viewing progress
- Combat service integration for kill objective tracking
Testing:
- Unit tests for Quest models and serialization
- Integration tests for full quest lifecycle
- Comprehensive test coverage for eligibility service
Documentation:
- Reorganized docs into /docs/phases/ structure
- Added Phase 5-12 planning documents
- Updated ROADMAP.md with new structure
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
6.5 KiB
6.5 KiB
Code of Conquest - Development Roadmap
Status: Active Development Last Updated: November 29, 2025
Overview
Code of Conquest is a web-based AI-powered Dungeons & Dragons style game where Claude acts as the Dungeon Master. This roadmap tracks development progress from MVP to public launch.
Tech Stack: Flask + Jinja2 + HTMX + Appwrite + RQ + Redis + Anthropic/Replicate APIs
Phase Summary
| Phase | Name | Priority | Status | Tasks |
|---|---|---|---|---|
| 1-4 | Foundation & Core Systems | - | ✅ Complete | - |
| 5 | Quest System | High | ⬜ Not Started | 14 |
| 6 | Story Progression & Lore | High | ⬜ Not Started | 22 |
| 7 | Multiplayer Sessions | Low | ⬜ Not Started | 25 |
| 8 | Marketplace | Medium | ⬜ Not Started | 17 |
| 9 | Frontend Polish | Medium | ⬜ Not Started | 19 |
| 10 | PWA & Deployment | High | ⬜ Not Started | 19 |
| 11 | Beta Testing | High | ⬜ Not Started | 17 |
| 12 | Launch Preparation | High | ⬜ Not Started | 19 |
Total Remaining Tasks: 152
Completed Phases (1-4)
Phase 1: Foundation
- ✅ Project setup (Flask, Appwrite, Redis)
- ✅ Authentication system
- ✅ User management
Phase 2: Character System
- ✅ Character creation with origins and classes
- ✅ Attribute system (STR, DEX, CON, INT, WIS, CHA)
- ✅ Skill trees with unlock mechanics
- ✅ Experience and leveling
Phase 3: Items & Inventory
- ✅ Item system with affixes and rarity
- ✅ Equipment and inventory management
- ✅ NPC shop system
Phase 4: AI Integration & Core Gameplay
- ✅ AI Dungeon Master integration
- ✅ Turn-based combat system
- ✅ NPC dialogue system with personality and knowledge
- ✅ Location and travel system
- ✅ Session management
- ✅ Action prompt system
Active Development
Phase 5: Quest System
Goal: YAML-driven quest system with context-aware offering
Key Deliverables:
- Quest data models (Quest, Objective, Reward, Triggers)
- 10+ quests in YAML format
- Context-aware quest offering during gameplay
- Quest acceptance, tracking, and completion
- Quest tracker UI
Phase 6: Story Progression & Lore
Goal: Vector database-powered NPC knowledge and world lore
Key Deliverables:
- Weaviate vector database integration
- World lore content (history, mythology, kingdoms)
- Regional lore for starter region
- NPC knowledge integration via RAG
- Knowledge filtering by NPC role/profession
Upcoming Phases
Phase 7: Multiplayer Sessions (Low Priority)
Goal: Invite-based, time-limited co-op sessions
- Premium/Elite tier only
- 2-4 player parties
- AI-generated campaigns
- Realtime synchronization
Phase 8: Marketplace
Goal: Player-to-player trading system
- Auction and fixed-price listings
- Bidding with notifications
- 5% marketplace fee
Phase 9: Frontend Polish
Goal: UI/UX improvements and design system
- Dark fantasy aesthetic
- Mobile-responsive design
- HTMX enhancements
- Reusable components
Phase 10: PWA & Deployment
Goal: Production deployment as Progressive Web App
- PWA with offline support
- Production infrastructure
- Monitoring and backups
Phase 11: Beta Testing
Goal: Gather feedback and stabilize
- 10-20 beta testers
- Bug fixing
- Balance tuning
- Performance optimization
Phase 12: Launch Preparation
Goal: Marketing, payments, and public launch
- Landing page
- Stripe integration
- Legal compliance
- Public launch
Future Phases (Post-Launch)
Phase 13: Content Expansion
- Additional player classes (Monk, Druid, Warlock, Artificer)
- New locations and quests
- More items and equipment
- Seasonal events
Phase 14: Advanced Features
- Guild system
- PvP arena
- Crafting system
- Achievement system
- World events
Phase 15: Mobile Apps
- Native iOS app
- Native Android app
- Mobile-specific optimizations
Success Metrics
MVP Success (End of Phase 10)
- 50+ beta users
- < 3s average API response time
- < $500/month AI costs
- 99% uptime
- < 5% error rate
Launch Success (End of Phase 12)
- 500+ registered users
- 100+ paying subscribers
- Positive user reviews
- Profitable (revenue > costs)
- Active community
Long-term Success (6 months post-launch)
- 5,000+ registered users
- 1,000+ paying subscribers
- Monthly content updates
- Growing user base
- Sustainable business model
Risk Management
| Risk | Impact | Probability | Mitigation |
|---|---|---|---|
| AI costs exceed budget | High | Medium | Daily monitoring, strict tier limits, cost alerts |
| Appwrite service issues | High | Low | Backup plan to self-host, regular backups |
| Low user adoption | Medium | Medium | Beta testing, marketing, community building |
| Performance issues | Medium | Medium | Load testing, horizontal scaling, caching |
| Security vulnerabilities | High | Low | Regular audits, security-first development |
| Feature creep | Medium | High | Stick to roadmap, resist scope expansion |
Related Documentation
Project-Wide:
- ARCHITECTURE.md - System architecture
- DEPLOYMENT.md - Deployment guide
- VECTOR_DATABASE_STRATEGY.md - Lore system design
API Backend:
- API_REFERENCE.md - API endpoints
- DATA_MODELS.md - Data models
- GAME_SYSTEMS.md - Game mechanics
- QUEST_SYSTEM.md - Quest specification
Web Frontend:
- TEMPLATES.md - Template structure
- HTMX_PATTERNS.md - HTMX patterns
Document Version: 2.0 Created: November 2025 Maintainer: Development Team