Context Is the Source of Truth.
Software Is the Deliverable.

With proper context saved, AI can re-build the solution with no intervention

Context Driven Development

AI-driven requirements interview captures intent as structured context
Context is created, reviewed, and approved before solutioning
Multi-AI solution design and project plan development
Tasks assigned to specialized AI subagents for parallel execution
All context saved on GitLab Kanban boards with human approval gates

THE PIPELINE

Five Phases of Context Driven Development

1
Requirements
2
Solution
3
Planning
4
Board Setup
5
Execution

Context flows forward through every phase — each step enriches the next

PHASE 1 — CONTEXT CAPTURE

AI-Driven Requirements Interview

📝

Structured Specification

Interview produces a formal requirements document. Reviewed and approved by the human before any solutioning begins.

🗣

AI Collaboration

An interactive session between human and AI to ensure the AI has a deep understanding of the vision and key requirements for a complete specification.

📋

GitLab Board Created

A dependency chain is automatically created on GitLab, tracking the feature from requirements through execution. Human controls pacing.

PHASE 2 — AI COLLABORATION

Multi-Model Solution Design

Gemini
Architecture & Workflows

Broad reasoning across system boundaries. Workflows, integration, scalability.

ChatGPT
Implementation & Feasibility

Code-focused analysis. Catches structural issues, validates feasibility.

Claude
Synthesis & Integration

Practical execution and infrastructure fit. Synthesizes into unified design.

When Does the Review Board Fire?

Solution design • Solution critique • Plan generation • Plan peer review • Architecture decisions • Spec validation • Debugging 2nd opinions

AI Review Board: Critique Loop

All three AIs attack the solution for over-engineering. Refactored and re-synthesized based on critique.

THE AI TEAM

Your AI Software Development Team

📋
PM
Orchestration
Coordination
Task sequencing
🏗
Architect
System design
ADRs
Integration
🛡
Security
Auth & secrets
Network rules
Compliance
💻
Developer
Code & Docker
Databases
Implementation
🧪
QA
Test specs
CI pipelines
Validation

Agents divide tasks and work in parallel — just like a real engineering team

PHASE 3 — PLANNING

Plan Vetted by 3 AIs, Tasks Assigned to 5 Agents

Gemini
+
ChatGPT
+
Claude
3 Independent Plans
Synthesized + Peer Reviewed
Final Plan
Agent Assignments + Dependencies
Tasks routed to specialized agents
📋
PM
Coordination
🏗
Architect
Design
🛡
Security
Auth & Network
💻
Developer
Implementation
🧪
QA
Validation

Grey areas flagged as DECISION cards for human judgment before execution begins

PHASE 4 — KANBAN BOARDS

Plan Becomes GitLab Cards

GitLab Kanban Board
GITLAB CI/CD

Every Commit Triggers a 5-Stage Pipeline

1 lint lint
Static analysis & code style enforcement. Blocks pipeline on violations.
2 test unit-test
263 unit test functions — full test suite must pass before build
3 build build
Docker image build & push to GitLab Container Registry
4 deploy deploy
Pull new image & restart container on linuxserver.lan
5 qa qa-e2e • qa-media • qa-smoke
Post-deploy Playwright tests against live service:
20 E2E test blocks • media pipeline checks • 9 smoke test functions
GitLab Pipelines List
GitLab Pipeline #612 Stages
PHASE 5 — EXECUTION

Board-Driven Workflow

👤
Human Review
Ready
In Progress
🏁
Done

Human in the Loop

AI never closes issues. Humans approve, reject, or redirect at every stage. DECISION cards pause execution until the human picks an option.

Free-Form Comments

Any card supports optional free-form comments. Check the "Read comment" box and the AI reads your feedback and adjusts course mid-task.

Context Is the Source of Truth.
Software Is the Deliverable.

Requirements
Solution
Plan
Board
Execute

With proper context saved, AI can re-build the solution with no intervention

Mike Murphy

Mike Murphy

linkedin.com/in/mikemurphynj