Retrospective Pipeline
Project Manager Official v1.1.27Collects feedback, analyzes themes, and produces action items
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 9 nodes
Retrospective Pipeline
Collects feedback, analyzes themes, and produces action items
Decision Documentation
Captures decisions with context, alternatives considered, and rationale
Decision Record Writer
Composing formal, archivable decision records in ADR format from the retrospective analysis and captured decisions
Retrospective Facilitation
Structures and analyzes retrospective feedback
Decision Record Writer
Task prompt for producing formal decision records
Facilitate Retrospective
Core prompt for structuring and analyzing retrospective feedback
Record Decision
Core prompt for capturing decisions with full context
Decision Record Template
Standard template for documenting project decisions
Retrospective Action Tracker
Tracks action items arising from sprint retrospectives
Requirements 1 service
- LLM Service
Security Passed
Detected
- Services: llm-service
- Permissions:
- Data Handling:
Version history 20 releases
GH#863 (Wave 1, batch 4) — fix the intent/output mismatch where the promised deliverable was never produced (K-045). The bundle shipped the `decision-record-writer` prompt — the step that writes up the formal, archivable decision records the workflow promises — and the docs said to run it, but the `execution:` block never invoked it, so that deliverable was silently dropped. Added a **Decision Record Writer** step (backed by a new `decision-record-composition` skill so it is `from_step`-addressable) as the terminal synthesis step, ordered `Facilitate Retrospective → Extract Action Items → Record Decision → Decision Record Writer`. Rewired the writer's inputs from positional `{{steps.<Title>.output}}` refs to explicit `from_step` bindings via `context_params` (`retrospective_analysis` ← Facilitate Retrospective, `decision_context` ← Record Decision). Completed the tail: repinned `polish-language` 1.0.1→1.0.6 (the version exposing the bindable `source` slot) and bound `language-polish`'s `source` ← the Decision Record Writer output, so the `output_step` polishes the actual decision record rather than its positional previous. No new required inputs.
GH#845 — republish with American English (en-US) content, completing the source-only GH#805 flip that never reached the Hub. Copy only — no functional or behaviour change.
GH#745 — declare per-step `output: {name, type}` on every execution step (retrospective/text, decision_record/text, action_items/list, polished_report/text). Lights up the #744 rich flow-map with named, typed outputs. Content-only; no bindings or logic changes.
GH#645 Row 3b — migrate to K-037 dep-referenced schema. Strip 6 inline shared-content files and declare 6 hub-shared deps (UUID id + slug name + version + checksum from `gen-dep-checksums.mjs`). Internal slug references rewritten for E2 rename/mirror-drop pair(s): sprint-ceremony-playbook→retro-playbook. Closes pre-Step-3 inline-vendoring for this bundle.
Wave 2: re-signed with canonical engine signing pipeline.
Signature fix — RELEASE_NOTES.md now included in integrity checksum.
Initial catalogue release with full structural and content-quality validation. All scanner checks pass.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
More from Project Manager
View all →Sprint Planning Pipeline
End-to-end sprint planning from backlog to committed plan
Jira Ticket Triage
Pulls Jira tickets via MCP, categorizes by status and priority, and generates a triage report or sprint summary
Status Report Flow
Gathers data, analyzes progress, and produces stakeholder updates