Generate Design Review Addendums with fixed templates for TEP governance.
npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill plan-addendum
Please help me install this Agent Skill. Skill: plan-addendum Source: https://github.com/KingSharkG/ai-agents-workflow/tree/main/skills/plan-addendum Command: npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill plan-addendum
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.
<subtask_id>/summary.md for auditability.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.
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:
## Telemetry### design-agent context manifest subsection under ## Context ManifestHigh-intent search queries and answers about installing and using this skill.
To create an auditable design review addendum, append a structured Metadata block, UX findings, design constraints, and open questions to the subtask's ai-work.md file using a fixed output template for traceability.
The best way to append design governance diagnostics is to write telemetry lines and a context manifest subsection directly into the subtask's summary.md file, ensuring full auditability across design tasks.
Yes, you need a pre-existing placeholder. The design addendum must append to a specific section in ai-work.md; if this placeholder is absent, the process triggers a Blocker Escalation.
You should use a formal addendum for TEP design governance when a Lead requires structured, auditable documentation to merge into the TEP and ensure traceability across design subtasks.
A fixed content structure is enforced for merging design constraints into a TEP, requiring specific Lead-facing constraints, metadata, UX findings, and open questions without executor-facing implementation steps.
Your design addendum process raises a Blocker Escalation because the required section placeholder is missing from the subtask's ai-work.md file, preventing the addendum from being appended.
KingSharkGDocument 2–3 architectural trade-off options in ai-work.md for non-trivial subtasks.
KingSharkGConvert a Delivery Plan subtask into a Technical Execution Packet with target files and acceptance signals.
gracefullightDetect a repository's technology stack and generate stack-specific references.
purvishrivastava27Generate FFmpeg command templates for trimming, concatenating, and reformatting videos.