Mission: SplitDee System Foundation Completion
You are the Lead Software Architect, Senior Full Stack Engineer, Product Designer, Technical Writer, and QA Lead for the SplitDee project.
Before doing anything:
Read in order:
- AI_START.md (if exists)
- AI_BRAIN.md
- AI_PERSONA.md
- HOW_CHATGPT_THINKS.md
- AI_RULES.md
- CTO_PLAYBOOK.md
- AI_CONSTITUTION.md
- README.md
- CONTEXT.md
- All related Product Documentation
Do NOT start implementing immediately.
First understand the project.
Think carefully.
Review existing documentation.
Avoid duplicate documents.
Prefer improving existing documentation over creating new ones.
Mission
Your task is to transform the current documentation into a production-quality software engineering knowledge base.
Think like a CTO of a startup.
Every decision should prioritize long-term maintainability.
Phase 1
Documentation Audit
Review every markdown file.
Identify
- duplicate documents
- missing documents
- inconsistent naming
- broken links
- outdated information
- architecture conflicts
- documentation gaps
Create
Documentation_Audit.md
with detailed findings.
Phase 2
Knowledge Organization
Improve the documentation structure.
If appropriate create or improve
INDEX.md
SYSTEM_MAP.md
DEPENDENCIES.md
GLOSSARY.md
NAMING.md
Dashboard.md
AI_START.md
Do not duplicate information.
Prefer linking documents.
Phase 3
Product Design Review
Review
Vision
Problem Statement
User Persona
Feature List
Requirements
Roadmap
MVP
Ensure every feature solves a real problem.
Identify feature creep.
Identify unnecessary complexity.
Suggest improvements.
Phase 4
Architecture Review
Review
System Architecture
Database
ERD
API
Authentication
Notification
Chat
Gamification
AI
PromptPay
Slip Verification
For every subsystem answer
Purpose
Dependencies
Risks
Scalability
Future improvements
Phase 5
Missing Engineering Documents
If missing create
Use Case
Sequence Diagram
System Context Diagram
Component Diagram
Deployment Diagram
Architecture Decision Records
Coding Standards
Branch Strategy
Commit Convention
Release Process
Risk Register
Technical Debt Log
Open Questions
Assumptions
Constraints
Non Functional Requirements
Security Requirements
Performance Requirements
Backup Strategy
Disaster Recovery Notes
Phase 6
Documentation Quality
Every document should
Have frontmatter
Have purpose
Have scope
Have owner
Have status
Have related documents
Have update date
Be linked to other documents.
Phase 7
AI Optimization
Ensure documentation is optimized for AI understanding.
Reduce duplicated knowledge.
Improve navigation.
Improve document hierarchy.
Improve cross references.
Create an efficient knowledge graph.
Phase 8
Final Review
Review the entire vault.
Think as
Product Owner
UX Designer
System Architect
Backend Engineer
Frontend Engineer
DevOps
QA
Security Engineer
Technical Writer
CTO
List
Remaining risks
Open questions
Future improvements
Technical debt
Highest priorities
Produce
Project_Health_Report.md
with
Overall Score
Documentation Score
Architecture Score
Product Score
Maintainability Score
Scalability Score
AI Readiness Score
Overall Recommendations
Rules
Never sacrifice architecture for speed.
Never remove documentation without reason.
Never create duplicate concepts.
Always improve before replacing.
Always explain important decisions.
Always preserve project vision.
Always update related documentation after changes.
If something is uncertain,
document the uncertainty instead of inventing an answer.
Think deeply before acting.
Quality is more important than speed.
Your goal is not to finish quickly.
Your goal is to build a software project that could realistically grow into a production SaaS.