---
name: "task-pulse-retro"
type: task
description: "Scheduled deployment of skill-ops-retro's author pass — the second of the two daily Pulse-retro passes, and the one that only produces and presents. Reads the author manifest task-pulse-refine emitted, and for each READY row re-reads live canon, match-checks the row's anchor, applies the specified change, validates frontmatter, packages the .skill, presents it for save, files any named repo-lane ticket, and closes the row's folded notes as incorporated; then logs decisions and writes a short report. Does no assessment, collation or blocker testing. Runs after task-pulse-refine. Loader only; behaviour lives in skill-ops-retro. Linear connector."
license: CC BY-NC-SA 4.0
---

# task-pulse-retro

Scheduled deployment of the Pulse retro **author pass** — the second of the two daily passes (the first is `task-pulse-refine`, the refine pass). This task carries no behaviour of its own — it is a loader.

**Read the canon artefact `skill-ops-retro` (the saved skill of that name; locally at `.claude/skills/skill-ops-retro/SKILL.md`) and follow it verbatim, in drain author mode.** The boundary rule: **if a step involves reading or a judgement call, it is the refine pass's; if it involves producing a package or saving, it is yours.** So: read the author manifest index (the os.Claude document `osclaude.pulse-manifest`); for each `READY` row, fan one tool-scoped subagent that reads the row's child document `osclaude.pulse-manifest.<target>` (the change set lives there, not in the index — a child not headed with this run's refine date is stale), re-reads the live canon the row targets, **match-checks** the row's anchor against it, applies the specified change, validates the frontmatter (4b), packages the `.skill` named exactly as the target, presents it for save, files the repo-lane ticket the row names (4a), and closes the row's folded notes as *incorporated* naming the exact change (5), returning a short summary — the package and any long output go to the session outputs folder as files, never back as a payload (`convention-agent-runtime`; APP-1098). In the parent, log the run's canon decisions (5a) and write the short report (6), stating that this session is the complete current save set. Before starting, also load `convention-linear` and `core-operating-model` so the queue rules and the save-vs-publish discipline are current.

**Run context:** scheduled autonomous run on the Linear connector, second of the day, after `task-pulse-refine`. **Do not re-assess, re-collate, or re-test blockers; do not touch the Blocked queue or an `OWNER-GATED` row.** Your only judgement is the match-check: a row whose anchor no longer matches live canon is kicked back — comment `[pulse-retro] stale — re-refine` on its folded notes, leave them in Backlog, move on. Propose only — never edit canon, never route a canon edit to Forge, never merge. If the manifest is absent or empty because the refine pass has not run, run the refine steps inline first and hold the manifest in-session rather than authoring against an unrefined queue.

**Reading the manifest:** the index document `osclaude.pulse-manifest` is read in a single `get_document` call, and each row's child document is fetched by its own title, `osclaude.pulse-manifest.<target>`. An index that cannot be read in one call is a hard stop to report — not a reason to improvise a partial run from whatever came back, and not a reason to reconstruct rows from the child titles alone. The 2026-09-04 index reached 56,083 characters and overflowed; the run says so and stops rather than authoring against a truncated queue.

**Every presented row is reconciled before the run reports.** For each `READY` row the pass presented, confirm that every folded note the row names was actually closed as *incorporated*, and name in the report any that were not. A row kicked back on a failed anchor match carries the same obligation: the `[pulse-retro] stale — re-refine` comment on its folded notes is mandatory and the notes stay in Backlog — never a silent drop. The report therefore states rows presented, folded notes closed, and rows kicked back as stale. Worked case, the 2026-09-03 author pass: `task-cycle-planning` (APP-1054) and `skill-plan` (APP-892) landed but their notes stayed in Backlog, each costing a full re-assessment; the `operator-bara` row was dropped on an un-matchable anchor with no comment, leaving APP-1064, APP-980 and APP-998 invisible until a grep — 5 notes affected across one pass.

*To change what the author pass does, edit `skill-ops-retro` — never this file or the scheduled-task config. Add steps here only if this task must ever sequence more than the single skill.*

## Final step — capture telemetry

On finish, read the canon artefact `skill-telemetry-capture` (the saved skill of that name; locally at `.claude/skills/skill-telemetry-capture/SKILL.md`) and follow it verbatim, passing `task: task-pulse-retro` and this run's own `outcome` (e.g. `completed`, `blocked`).