CTO/docs/AGENT-LLM.MD

AI AGENT REFERENCE - TEMPLATE VERSION

FOR: Gemini-CLI, Claude, OpenCode, all AI tools working with CTO delegation template

CRITICAL SETUP (FIRST TIME ONLY)

This template requires initial git setup:

git init
git add .
git commit -m "Initial commit from CTO template"
git branch -M main
git remote add origin YOUR_REPO_URL
git push -u origin main

Create required branches:

git checkout -b INTEGRATION-WIP && git push -u origin INTEGRATION-WIP
git checkout -b RELEASE && git push -u origin RELEASE  
git checkout main

CRITICAL RULES

1. NEVER work on main branch - Always use feature branches
2. NEVER auto-delete feature branches - Preserve all branches permanently
3. ALWAYS push before switching branches - Never lose work
4. Push every 10 commits max - Keep work backed up
5. Tag milestones - Mark completed stages/milestones
6. UPDATE WORKLOGS - Maintain both worklog files

DETERMINISTIC COMMANDS

Start new feature (EXACT sequence):

git checkout main
git pull origin main  
git checkout -b feature/TASK-NAME

Save work before switching (MANDATORY):

git add .
git commit -m "SPECIFIC_DESCRIPTION_OF_CHANGES"
git push origin CURRENT-BRANCH-NAME

Tag completed milestone:

git tag -a MILESTONE-NAME -m "DETAILED_DESCRIPTION_OF_COMPLETION"
git push origin MILESTONE-NAME

BRANCH STRUCTURE (CREATE THESE)

• main - Stable, protected, no direct commits
• INTEGRATION-WIP - Auto-merge target for testing features
• RELEASE - Manual PR target for production releases
• feature/TASK-NAME - All development work (descriptive names)

DETERMINISTIC WORKFLOW

1. Always start from main: git checkout main && git pull origin main
2. Create specific branch: git checkout -b feature/EXACT-TASK-NAME
3. Work in small chunks: Commit every logical change
4. Push frequently: Every 5-10 commits or before any branch switch
5. Never delete branches: Preserve all feature branches permanently
6. Tag milestones: When features/stages complete

MILESTONE TAGGING (DETERMINISTIC)

When to tag:

• Feature completely implemented and tested
• Stage of project fully complete
• Major milestone achieved

Format (be specific):

• feature-auth-complete (feature done)
• milestone-YYYY-MM-DD-DESCRIPTION (date+description)
• stage-NAME-done (stage complete)

WORKLOG MAINTENANCE (MANDATORY)

Update these files every session:

• docs/WORKLOG-LLM.md - Current status, progress, next actions
• docs/CURRENTWORK-LLM.md - Detailed notes, decisions, concerns

Pattern (deterministic):

1. Session start → Update current status in WORKLOG-LLM.md
2. During work → Add detailed notes to CURRENTWORK-LLM.md
3. Session end → Update completion status and next actions

CTO DELEGATION PRINCIPLES

Make outcomes deterministic:

• Use specific commit messages describing exact changes
• Tag with descriptive names explaining what was accomplished
• Document all decisions and concerns in CURRENTWORK-LLM.md
• Follow exact command sequences above
• Never deviate from branch protection rules

CONTEXT

• Purpose: Template for CTO AI delegation framework
• Platform: Any git hosting (GitHub, Gitea, GitLab)
• Structure: Keep docs in docs/ directory for clean repos
• Philosophy: Deterministic AI delegation with complete audit trail