**Status:** Draft for review **Author:** Aidan Foster **Date:** 2026-07-20 --- **Note:** Depends on https://git.drupalcode.org/project/ai_content_review/-/work_items/3585841 ## 1. Purpose Step 2 of the two-step workflow: after building the improvement plan in the review tray (#3585830), the editor opens the edit form and applies their accepted suggestions by hand. v1 is deliberately simple — a checklist with an easy copy button, no automated interaction with field widgets. The value is that the editor arrives at the edit form with a concrete, ordered plan instead of a memory of what the review said. ## 2. Scope ### In scope * The "AI content improvement plan" checklist in the node edit form's sidebar. * Per-task done checkboxes, expand/collapse, before → after diff, and copy-to-clipboard. * Progress footer ("N of M complete"). * Persistence of done-state with the review run's decisions. ### Out of scope * Any automated application of suggestions to fields ("no magic" in v1) — see §10. * Building the plan (triage) — #3585830. * Generating findings — #3585828. * The Content Review sidebar accordion itself (per-criterion scores, "Last review") — same component set as #3585828, shown here in its edit-form placement. ### Assumptions * Accepted decisions — including edited suggestion text from the tray's inline editor — are readable from the triage step (#3585830 §9). * The editor arrives either via the tray's "Apply the changes" CTA or by opening the edit form directly. ## 3. Entry workflows ### Workflow A — Arriving from the tray CTA "Apply the changes" (#3585830 T3) opens the node edit form with the improvement-plan accordion open and the first task expanded. ### Workflow B — Opening the edit form directly If a plan with accepted tasks exists for the current run, the accordion is present in the sidebar with prior done-state intact. ## 4. Layout and components ### 4.1 Placement * A sidebar accordion on the node edit form (Gin), labeled along the lines of **"AI content improvement plan"**. * Sits alongside the existing Content Review accordion (per-criterion scores, "Last review" timestamp). ### 4.2 The checklist * **Only accepted tasks appear** (e.g. 8 of 10 findings; ignored and reported findings are excluded). Edited suggestion text from the triage step carries through. * Task titles are rewritten as **imperative actions** ("Extend the title to fill your SEO length target") rather than the finding titles from the tray — the tray describes problems, the checklist describes work. * Each task row: criterion color rail, **done checkbox**, title, expand/collapse chevron. One task expanded at a time. * Expanded body: rationale, then the before → after diff, with a **copy-to-clipboard button** on the suggested text (with "Copied!" confirmation). Copy is the core affordance — the editor pastes into the right field themselves. * Header hint: "Check off each task as you apply it in the editor." ### 4.3 Progress footer * Progress bar with "N of M complete". ## 5. States | ID | State | Trigger | Visible appearance | |----|-------|---------|--------------------| | S1 | No plan | No accepted tasks exist for the current run | Accordion absent (or collapsed empty note — see §12) | | S2 | In progress | Plan exists, not all tasks done | Task list with done/undone rows, progress bar | | S3 | Task expanded | Row clicked | Rationale + diff + copy button; other rows collapse | | S4 | Complete | Every task checked | Progress at 100% (whether this prompts anything is an open question, §12) | ## 6. Interactions ### 6.1 Check off a task Checking marks it done (strikethrough, tinted row) and updates progress; reversible. ### 6.2 Expand / collapse Clicking a row toggles its body; one task expanded at a time. Keyboard: Enter/Space on the row header. ### 6.3 Copy The copy button places the suggested text (post-edit version) on the clipboard and confirms with "Copied!". ## 7. Persistence * Done-state persists with the review run's decisions, so leaving and returning to the edit form keeps progress. * A new review run replaces the plan (consistent with #3585828 re-run semantics). ## 8. Edge cases * **Empty plan** (everything ignored/reported in triage): see S1 / §12. * **Suggestion edited in the tray:** the checklist shows the edited text; the "before" side remains the original page text. * **Prose-style tasks** (e.g. missing alt text) render the diff as description → suggested value rather than strikethrough text. * **Plan open while content is edited:** the checklist is a static list; it does not re-validate against the changing field values (future scope). ## 9. Data and API surface (referenced, not specified here) This functional doc does not name or assume specific entity types, fields, or method signatures. What this surface needs: * Read access to accepted decisions (including edited suggestion text) from #3585830. * Storage of per-task done-state, tied to the review run. * The imperative task-title rewrite (who generates it — same agent run or a rewrite pass — is an open question, §12). ## 10. Nice-to-have / future scope Recorded so the v1 simplicity reads as sequencing, not the end state: 1. **"Do it for you" in the Drupal UI** — a task offers an Apply action: the AI applies the suggested change to the correct field, or opens a chat to refine it first (future-state sketched May 15: click a task → scroll to the field → apply recommendation, change, or chat about it). 2. **Drupal Canvas AI chat** — inside Canvas, the AI chat could support applying these same updates conversationally. 3. Lighter intermediate step: clicking a task scrolls to / focuses the corresponding field even while application stays manual. 4. Re-validating done tasks against actual field content; prompting a re-run when all tasks are complete. A separate roadmap note / meta-issue should track 1–2 once v1 lands. ## 11. Acceptance criteria The feature is functionally complete when an editor can, on the node edit form: 1. Arrive from the tray's "Apply the changes" CTA and find the improvement-plan accordion open with only accepted tasks listed. 2. Read each task as an imperative action, expand it, and see rationale plus the before → after diff (edited suggestion text where applicable). 3. Copy the suggested text with one click and get a "Copied!" confirmation. 4. Check tasks off (and uncheck them) with progress updating. 5. Leave and return with done-state intact. 6. See the plan replaced when a new review run completes. ## 12. Open questions * Accordion label and default-open behavior when arriving from the tray CTA. * Who generates the imperative task-title rewrite — same agent run, or a rewrite pass? * Empty-plan handling: hide the accordion entirely, or show an empty note? * Does completing all tasks feed anything (e.g. prompt to re-run the review)? * A11y: checkbox semantics, accordion keyboard behavior, copy-button announcement. ## 13. Screenshots {width=900 height=528} The "Accepted" improvements show up here {width=900 height=532} Working though the items updates process bar, We do this manually (for now) {width=360 height=527} Open by default unless 100% completed ## 14. Claude design — standalone HTML export [Blog Apply Improvements (standalone).html](/uploads/d0550183d189b649f82ccbcf718dda7a/Blog_Apply_Improvements__standalone_.html) * `Blog Apply Improvements (standalone).html` — the edit-form checklist mockup these behaviors come from. ## Video (Entire workflow) https://zoom.us/media/share/VyxVIvnSRYeej3U8lsSySQ?module=clips&product=video-center --- _Sources: AI review working sessions May 15 and May 22, 2026 (two-step decision, "no magic" v1, Google-tasks-style checklist, copy-button idea); apply-step UI export July 19, 2026. Comp explorations done in Claude Code._