Chat Closure Agent Implementation — Epic

Overview

Build a reusable Tier 1 portable agent that automates chat session closure workflows across control-plane and WordPress repositories.

Problem

Long-running Claude Code sessions hit context limits, requiring manual closure:

• Gather scattered context (projects, issues, PRs, branches, memory)
• Create continuation prompts from scratch
• Update memory and clean up worktrees
• Archive chats manually

Solution

Chat Closure Agent automates all steps:

• ✅ Analyze git state (branch, commits, issues, projects)
• ✅ Extract metadata (repo type, scope, decisions)
• ✅ Update memory (10-family YAML structure)
• ✅ Generate handoff prompt (Markdown)
• ✅ Clean worktree (with user confirmation)

Scope

• Repo types: Control-plane, WordPress plugins, WordPress themes
• Agent framework: Tier 1 portable (multi-file, reusable)
• Test target: ≥85% coverage
• Timeline: 4 weeks (40-50 hours)

Design Decisions (Finalized)

1. Memory depth: Moderate (summary + links)
2. Worktree delete: Ask before deleting
3. Memory linking: One-way (memory→issue)
4. WordPress support: Both plugins & themes equally
5. Chat archival: Manual step (future API ready)

Implementation Phases

Success Criteria

✅ 85%+ test coverage (Jest)
✅ All 3 repo types working
✅ Full workflow end-to-end
✅ Comprehensive docs with Mermaid diagrams
✅ Real-world example workflow

Related Resources

• Project Documentation
• PR #1801 — Planning & Project Setup

Status: Epic in planning → Phase 1 implementation
Effort: 40-50 hours

Definition of Ready (DoR)

• Epic vision and scope clearly defined
• Success criteria and measurable outcomes documented
• High-level tasks/stories identified
• Dependencies and risks mapped
• Timeline and resource estimates provided
• Stakeholder alignment confirmed

Epic Owner / Sponsor

Sponsor/Owner: [Who is driving this epic]

Success Owner: [Who validates completion]

Success Criteria

• All Phase milestones achieved
• Stakeholder sign-off obtained
• Team capacity and velocity met targets

Definition of Done (DoD)

• All child issues/stories completed
• Epic acceptance criteria met
• Epic documentation and summary updated
• Release notes and announcement prepared
• Post-launch monitoring and support plan in place
• Retrospective completed (if applicable)

Spec 020 programme alignment — Tier 8

Reconcile this implementation epic with GIT-79 before creating children or selecting a canonical parent. Preserve both records’ history; overlapping descriptions alone do not establish a safe duplicate marking.

Separate read-only session analysis and handoff drafting from memory writes and worktree cleanup. Preview exact changes and obtain approval before mutation or deletion; preserve uncommitted work and unrelated worktrees. Keep archival manual unless an available, authorised capability is verified.

Historical durations, coverage targets and completion symbols are planning claims, not current delivery evidence.

Programme Tier 8 describes delivery sequencing, not native priority or historical portability classifications. Each delivery slice must record its exact branch and base, PR title, live template, verified labels, assignee, changed-file scope, tests and closure criteria before implementation. Reuse matching existing work. Stack PRs only for a demonstrated dependency, with merge and retargeting order documented.