blog-author-triggerlisted

Operationalises spec/project/blog-author-trigger/: on a feature→done transition it derives a blog-post briefing from the feature record, computes a new/update/defer suggestion from the blog consumer's existing-post index, presents the three-way operator choice, and either dispatches blog-author with the derived briefing (Choices 1 and 2, via the cross-repository handover with explicit operator confirmation) or writes a deferral artefact under project/blog-triggers/ (Choice 3). Typically automatically dispatched by sprint-execute right after a feature reaches done; also invocable directly ("trigger a blog post for feature X", "Blog-Trigger für Feature X", "soll ich zu Feature X bloggen?"). Don't use to draft the post itself (use blog-author), to define the feature record (feature spec), to close a sprint (sprint-review), or to publish a release (release-publish-trigger). Supports resume on re-invocation per spec/claude/resumable-work/.
nolte/claude-shared · ★ 0 · API & Backend · score 76

Install: claude install-skill nolte/claude-shared

# Blog Author Trigger Operationalises `spec/project/blog-author-trigger/<canonical_language>.md`: the **when** layer that bridges a `feature → done` transition in a source consumer (a `claude-shared`-shape repository with `project/features/`) to the **what** layer, `blog-author`, which drafts the bilingual post pair in a blog consumer (reference: `nolte/blog`). The trigger spec is contract-only and leaves the wiring mechanism open; this skill is the reference wiring per the spec's §Open questions resolution — a dedicated trigger skill that `sprint-execute` automatically dispatches after it writes a feature's `done` status. This skill binds the spec's contract to an on-disk procedure. When this skill and the spec disagree, the spec wins and this skill needs the update. ## Why this is a skill, not an agent - **Mid-flow operator decision is load-bearing** — the spec's §Operator decision contract requires the operator to answer exactly one of three choices (new post / update existing post / defer to backlog) at the trigger point, in the same session; an agent's fire-and-forget shape can't carry that gate. - **Cross-repository handover is an externally-visible action under confirmation** — Choices 1 and 2 hand off to a separate blog-consumer working tree; the spec forbids silent writes there, so the working-directory switch needs operator confirmation that only a conversational skill surfaces. - **Orchestrator that dispatches another skill** — Choices 1 and 2 dispatch `blog-au