plan-addendum

What problem does it solve?

Produces a structured Design Review Addendum for subtasks in design-hook domains. Use when the Design Agent must emit an auditable addendum that Lead will merge into the TEP.

Core Features & Use Cases

• Append inside the subtask's ai-work.md the design-addendum placeholder and a detailed Metadata block, followed by UX findings, design constraints, and open questions as required by governance.
• Write diagnostics (telemetry and context manifest) to <subtask_id>/summary.md for auditability.
• Enforce content structure with a fixed Output Template to ensure consistency in governance documentation.

Quick Start

Append the addendum to the subtask's ai-work.md using the predefined template and emit diagnostics to the subtask's summary.md.

Output Target

Append to <!-- section:plan-addendum --> in the subtask's ai-work.md. The placeholder MUST already exist — if absent, raise a Blocker Escalation. Also write diagnostics (telemetry line + context manifest subsection) to <subtask_id>/summary.md.

Output Template

Append inside <!-- section:plan-addendum -->:

<!-- section:design-metadata -->
## Metadata
- **task_id**: <from spec section>
- **subtask_id**: <from spec section>
- **agent**: design-agent
- **created_at**: <ISO 8601 UTC>
<!-- /section:design-metadata -->

<!-- section:design-findings -->
## UX Findings
- <finding or "none">
<!-- /section:design-findings -->

<!-- section:design-constraints -->
## Required Constraints for TEP
- <specific Lead-facing constraint to merge into the TEP>
<!-- /section:design-constraints -->

<!-- section:design-open-questions -->
## Open Questions
- <question or "none">
<!-- /section:design-open-questions -->

Then write diagnostics to <subtask_id>/summary.md:

• Append your telemetry line under ## Telemetry
• Append your ### design-agent context manifest subsection under ## Context Manifest

Rules

• Write the addendum content first, then finalize manifests and telemetry.
• Keep the content specific enough that the Lead can merge it into the TEP without follow-up questions.
• Do not emit executor-facing implementation steps.