Skip to content

completion.md

Latest commit

 

History

History
173 lines (119 loc) · 4.47 KB

completion.md

File metadata and controls

173 lines (119 loc) · 4.47 KB
Raw

Agent [X] — [CODENAME]: Sprint [XX] Completion Report

Branch: sprint-[XX]/[agent-name] Date: [YYYY-MM-DD] Status: COMPLETE | PARTIAL | BLOCKED

Summary

[2-3 sentences: What was accomplished. What wasn't and why. Any surprises or discoveries.]

Tasks Completed

Task ID Title Priority Status Files Changed
[X]-01 [title] P1 COMPLETE [count]
[X]-02 [title] P1 COMPLETE [count]
[X]-03 [title] P2 COMPLETE [count]
[X]-04 [title] P2 PARKED — [reason] 0

Task Details

[X]-01: [Title] — COMPLETE

What was wrong: [Root cause — one sentence]

What changed:

  • path/to/file.ts — [specific change, e.g., "Implemented JWT validation in canActivate(), replacing stub that returned true"]
  • path/to/other.ts — [specific change, e.g., "Updated to read workspaceId from guard instead of request body"]

Verification:

  • Build passes: [command] — PASS
  • Tests pass: [command] — PASS

[X]-02: [Title] — COMPLETE

What was wrong: [Root cause]

What changed:

  • path/to/file.ts — [change]

Verification:

  • Build: PASS
  • Tests: PASS

[X]-03: [Title] — PARKED

Reason: [Why this task was not completed — dependency, blocker, time, retry exhaustion] Retry history: [How many retries were attempted and what was tried] Recommended next step: [What the next agent or sprint should do]

Parked Chains (Retry Exhaustion)

Chains that failed after 3 retry attempts. This section feeds the convergence loop.

[X]-04: [Title] — PARKED (3 retries exhausted)

Attempt 1: [What was tried] → Failed: [error summary] Attempt 2: [Different approach tried] → Failed: [error summary] Attempt 3: [Fresh approach tried] → Failed: [error summary]

Failure analysis: [Why does this keep failing? Best hypothesis for the root cause. Is the trace wrong? Is the root cause somewhere else? Is there a dependency that wasn't accounted for? This information helps the convergence loop plan a better approach for the next iteration.]

What would I try differently: [If given another chance with more context, what approach would you try?]

P0 Discoveries

Issues discovered during work that were NOT in the original task list. These are critical findings that the operator and LEAD must review before merging.

ID Description File Line Risk Recommended Agent
P0-[X]-01 [what you found] [path] [line] [why it's critical] [who should fix]

If no P0 discoveries, write: "None discovered."

Issues for Other Agents

Non-critical findings that other agents should be aware of.

Issue Priority Recommended Agent Notes
[description] P1/P2/P3 [AGENT_NAME] [context — e.g., "Found during [X]-02, outside my territory"]

If none, write: "None."

Files Modified

Complete list of every file changed, created, or deleted:

MODIFIED  [path/to/file1.ts]
MODIFIED  [path/to/file2.ts]
CREATED   [path/to/new-file.ts]
DELETED   [path/to/dead-file.ts]

Verification Results

# Build
$ [build command]
# Result: PASS / FAIL

# Tests
$ [test command]
# Result: PASS — [N] tests passed, [N] failed, [N] skipped

# Lint
$ [lint command]
# Result: PASS / FAIL

# Territory check
$ git diff --name-only main..HEAD
# All modified files are within declared territory: YES / NO

Metrics

  • Tasks assigned: [N]
  • Tasks completed: [N]
  • Tasks parked: [N]
  • Files modified: [N]
  • Files created: [N]
  • Files deleted: [N]
  • Lines changed: +[added] / -[removed]
  • Tests added: [N]
  • Build status: PASS / FAIL
  • Test status: PASS / FAIL ([N] total, [N] passed)