Waterfall Day

Gate rule:

• If required architecture skill is not applied and evidenced, status must be blocked.
• Do not mark code, test, or deploy as done without architecture evidence.

Inputs Required

Collect these first:

1. run_date (YYYY-MM-DD)
2. project_scope (what must move today)
3. checklist_items (small, concrete tasks)
4. agent_pool (who is sub leader, dev, tester)
5. report_target (UI only, Telegram only, or both)

If an input is missing, ask for the minimum missing field and continue.

Roles

Sub Leader Agent

• Creates daily checklist and acceptance criteria.
• Reviews each phase handoff.
• Decides pass/fail to move forward.
• Publishes end-of-day report.

Developer Agent

• Implements only items approved up to design.
• Submits code summary and self-check.
• Returns task to tester with reproducible test instructions.

Tester Agent

• Executes tests (httpie preferred).
• Captures evidence (command, status, output).
• Returns pass/fail with bug notes.

Non-Negotiable Rules

1. Never skip a phase.
2. One checklist item can only have one active phase at a time.
3. test can move to deploy only if all required tests pass.
4. If test fails, move back to code.
5. Every phase must produce an artifact.
6. Every coding item must declare scope_type (frontend_only|backend_only|fullstack|docs_only).
7. Required clean-architecture skill evidence is mandatory for design, code, test, and deploy.

Execution Protocol

Step 1 - Daily Kickoff (Sub Leader)

Produce:

• Daily objective
• Prioritized checklist
• Definition of done per item

Template: references/waterfall-day-templates.md -> Kickoff Template

Step 2 - Requirement

For each checklist item, write:

• Problem statement
• Constraints
• Acceptance criteria

Status transition:

• pending -> in_progress -> done

Step 3 - Analysis

Write:

• Root cause / context
• Impacted modules
• Risk list

Output must contain at least one rollback/risk handling note.

Step 4 - Design

Write:

• API/data flow changes
• DB/schema impact (if any)
• Test strategy draft
• Architecture scope mapping:
  • scope_type
  • required skill path(s)
  • boundary checks planned

No coding until design is approved by sub leader.

Step 5 - Code (Developer)

Write:

• Implementation summary
• Changed files
• Self-check notes
• Architecture evidence:
  • which required skill(s) were applied
  • boundary checks executed and result

If blocked, return status blocked with reason and required decision.

Step 6 - Test (Tester)

Use reproducible commands (httpie first). Minimum artifacts:

• command executed
• status code / output
• pass/fail verdict
• architecture regression check result (if code changed)

Template: references/waterfall-day-templates.md -> Test Execution Template

Step 7 - Deploy Decision (Sub Leader)

If pass:

• mark deploy: done (or ready_for_deploy if deployment is manual)

If fail:

• return to code with bug checklist

Step 8 - End-of-Day Report

Triggered when user says equivalent of:

• "bao cao cuoi ngay"
• "end of day report"

Generate:

1. Full markdown report for UI
2. Short Telegram summary

Template: references/waterfall-day-templates.md -> EOD Report Template

Standard Status Model

Use only these statuses:

• pending
• in_progress
• done
• failed
• blocked
• cancelled

Output Contract (Per Checklist Item)

Always return this structure:

[ITEM] <id> - <title>