Current Task

Create

SPRINT1_EXECUTION_GUIDE.md

This is NOT an implementation task.

No PHP code shall be written.

No source code shall be modified.

No architecture shall be changed.

No governance shall be modified.

This document defines HOW Sprint 1 implementation will be executed.

It is an execution handbook for AI agents and human reviewers.

---

Mandatory References

Read completely before writing:

- AI.md v1.1
- AI_DEVELOPMENT_SYSTEM.md v1.0
- WORKFLOW.md
- PROJECT.md
- MASTER_IMPLEMENTATION_BACKLOG_v1.1
- DBP_v1.1
- SPRINT0_ARCHITECTURE_REVIEW.md
- SPRINT1_PLANNING.md

---

Objective

Produce the official execution guide for Sprint 1.

Sprint 1 starts from a frozen framework.

No Sprint 0 document may be modified.

Every Sprint 1 implementation must follow this guide.

---

Include the following sections.

# 1

Purpose

Explain the objective of this guide.

Explain that Sprint 1 focuses on implementation speed while preserving architecture quality.

---

# 2

Sprint 1 Scope

Summarize:

- objectives
- deliverables
- boundaries

Clearly state what Sprint 1 does NOT include.

---

# 3

Task Execution Workflow

Document the complete workflow.

Task

↓

Prompt

↓

Implementation

↓

Implementation Report

↓

Architecture Review

↓

Approval

↓

Git Commit

↓

Git Push

↓

Memory

↓

Next Task

---

# 4

Mandatory Reading Before Every Task

List every required document.

Explain why each must be reviewed.

---

# 5

Implementation Checklist

Before coding.

During coding.

After coding.

Before approval.

Before Git.

---

# 6

Review Checklist

Architecture

Coding Standards

Security

Scope

Files Expected

Acceptance Criteria

Documentation Deviations

---

# 7

Git Workflow

Standard commit sequence.

Standard push sequence.

Tag policy.

Branch policy.

Explain that Git commands require explicit human approval.

---

# 8

Prompt Standards

Describe the standard structure of implementation prompts.

Mandatory sections.

Forbidden sections.

Expected output.

---

# 9

Implementation Report Standard

Define the required report format.

Exactly:

1.

Implementation Summary

2.

Files Created

3.

Files Modified

4.

Acceptance Criteria

5.

Definition of Done

6.

Proposed Commit

7.

Documentation Deviations

---

# 10

Quality Gates

Per-task

Per-sprint

Before merge

Before release

---

# 11

Handling Documentation Conflicts

Summarize the official conflict protocol.

STOP

↓

Explain

↓

Reference Documents

↓

Wait for Approval

---

# 12

Handling AI Account Rotation

Explain:

Session Resume

Repository as Source of Truth

Memory Files

Response Archive

Context Recovery

Model Independence

---

# 13

Sprint Completion

Explain:

When a Sprint is considered complete.

Required artifacts.

Required reviews.

Required approvals.

---

# 14

Future Sprints

Explain that every future sprint inherits this execution methodology unless superseded by an approved Design Revision Pack.

---

# 15

Final Statement

State that this document is the operational handbook for Sprint execution and complements—not replaces—the governance documents.

---

Rules

Do NOT modify governance.

Do NOT redesign Sprint 1.

Do NOT introduce new implementation rules.

Document only practices already approved.

Maintain terminology.

Maintain writing style.

This document should be usable by any AI Implementation Agent immediately.

---

Output

Produce:

SPRINT1_EXECUTION_GUIDE.md

Then provide:

- Sections created
- Operational workflow summary
- New governance introduced (expected: none)
- Architecture changes (expected: none)

Nothing else.