@olegkoval/agent-skills 1.33.0 → 1.35.0

package/{packages/marketing/website-analytics-bootstrap/adapters/kiro/steering/website-analytics-bootstrap.md → .github/prompts/website-analytics-bootstrap.prompt.md}

@@ -1,10 +1,11 @@
 <!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
 
 ---
-inclusion: manual
 description: "Set up a website's first SEO analytics loop with persistent SerpBear rank tracking, Google Search Console, seeded keywords, read-only technical audits, and Telegram alerts on a local host or NAS."
 ---
 
+Use the olko:website-analytics-bootstrap skill.
+
 > 🤖 *Auto-generated by **weekly-pattern-learner** · reusable first-run website analytics onboarding workflow derived from a validated local/NAS setup pattern*
 
 # website-analytics-bootstrap

package/{packages/software-development/wikipedia-uk-editor/adapters/kiro/steering/wikipedia-uk-editor.md → .github/prompts/wikipedia-uk-editor.prompt.md}

@@ -1,10 +1,11 @@
 <!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
 
 ---
-inclusion: manual
 description: "Draft policy-compliant Ukrainian Wikipedia edits — translate an English article into uk, expand or source an existing uk article, or fix a maintenance backlog item — and return ready-to-paste wikitext plus an edit summary."
 ---
 
+Use the olko:wikipedia-uk-editor skill.
+
 # Ukrainian Wikipedia Editor
 
 Turn a URL or article title into a complete, policy-compliant Ukrainian Wikipedia edit that the human pastes into the wiki editor themselves.

package/{packages/software-development/wrap-up/adapters/windsurf/rules/wrap-up.md → .github/prompts/wrap-up.prompt.md}

@@ -4,6 +4,8 @@
 description: "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches."
 ---
 
+Use the olko:wrap-up skill.
+
 # Wrap Up
 
 Run this skill manually from time to time or as the final step after a task reaches its goal. It is a delivery audit and cleanup pass, not permission to expand scope or hide unfinished work.
@@ -56,20 +58,40 @@ Clean only paths created by this task or explicitly named for cleanup.
 
 ## 6. Report the result
 
-Lead with the outcome. Include concise evidence, cleanup performed, items intentionally preserved, and the smallest next action for any blocker. Always finish with this receipt, using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable checks that were not executed:
+Lead with the outcome. Use a short `DELIVERY RECEIPT` heading and a one- or
+two-sentence summary before the fields. Add `STATUS`, `NEXT_PHASE`, and
+`NEXT_STEP` near the top when follow-up work remains. Keep the required fields
+flush-left and grouped with one blank line between logical groups, not between
+every field. Keep each value concise and avoid repeating the same prose. Do
+not use Markdown tables, decorative separators, bullets, emojis, or indented
+continuation lines inside the canonical field block. Put `FINAL_STATUS` last.
+Add `LOCAL_COMMIT` when a local commit exists. Always finish with this receipt,
+using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable
+checks that were not executed:
 
 ```text
+DELIVERY RECEIPT
+
+<short outcome summary>
+STATUS: <DELIVERED | BLOCKED | INTENTIONALLY_UNCHANGED>
+NEXT_PHASE: <next phase or NOT_APPLICABLE>
+NEXT_STEP: <single smallest next action or NOT_APPLICABLE>
+
 OBJECTIVE:
 CHANGED:
 NOT_CHANGED:
+
 TESTS:
 BUILD:
+
 REMOTE:
 PR:
 CI:
 DEPLOYMENT:
 DEVICE_OR_HUMAN_QA:
+
 KNOWN_LIMITATIONS:
+LOCAL_COMMIT: <hash and subject, or NOT_APPLICABLE>
 FINAL_STATUS:
 ```
 

package/.grok-plugin/index.json

@@ -2,234 +2,59 @@
   "name": "agent-skills",
   "plugins": [
     {
-      "name": "olko:self-critique",
-      "source": "./packages/software-development/self-critique/adapters/grok",
-      "description": "Adversarially critique your own last answer: spawn a critic agent that verifies claims against live sources, finds the related issue or pattern you missed, then loop until satisfied and report where you were wrong, iterations-to-satisfy, the numeric improvement, and a final score."
+      "name": "olko-github-pr",
+      "source": "./adapters/grok/olko-github-pr",
+      "description": "Drive GitHub pull requests to merge-ready: review-bot loops, CI fixes, descriptions, dependency triage."
     },
     {
-      "name": "olko:docs-index-keeper",
-      "source": "./packages/software-development/docs-index-keeper/adapters/grok",
-      "description": "Keep a Markdown docs index in sync through pre-commit, CI, or one-off maintenance flows."
+      "name": "olko-git-tools",
+      "source": "./adapters/grok/olko-git-tools",
+      "description": "Everyday git and GitHub CLI operations: conventional commits, branch hygiene."
     },
     {
-      "name": "olko:semantic-release-beta",
-      "source": "./packages/software-development/semantic-release-beta/adapters/grok",
-      "description": "Set up semantic-release-npm-github-publish with stable main releases and prerelease beta releases on a beta branch."
+      "name": "olko-release",
+      "source": "./adapters/grok/olko-release",
+      "description": "Ship a release: semantic-release setup, changelogs, store listing copy, release-day routine."
     },
     {
-      "name": "olko:gh-cli",
-      "source": "./packages/software-development/gh-cli/adapters/grok",
-      "description": "Use the GitHub CLI effectively for repositories, PRs, Actions, releases, and more."
+      "name": "olko-product",
+      "source": "./adapters/grok/olko-product",
+      "description": "Take a product idea to a shippable build: MVP passes, full-stack scaffolds, launch plans."
     },
     {
-      "name": "olko:git-commit",
-      "source": "./packages/software-development/git-commit/adapters/grok",
-      "description": "Create conventional commits with diff-aware staging and message generation."
+      "name": "olko-skill-meta",
+      "source": "./adapters/grok/olko-skill-meta",
+      "description": "Author and maintain agent skills and the AI toolchain itself."
     },
     {
-      "name": "olko:gallery",
-      "source": "./packages/photography/gallery/adapters/grok",
-      "description": "Create photo galleries with AI-assisted layout curation and sequencing."
+      "name": "olko-reflection",
+      "source": "./adapters/grok/olko-reflection",
+      "description": "Look back and improve: self-critique, retrospectives, performance review, rapid learning."
     },
     {
-      "name": "olko:promptctl",
-      "source": "./packages/software-development/promptctl/adapters/grok",
-      "description": "Use promptctl for template-based prompt engineering, scoring, and workflow automation."
+      "name": "olko-obsidian",
+      "source": "./adapters/grok/olko-obsidian",
+      "description": "Keep an Obsidian vault in sync with work: PR sync, task rollover, morning routine."
     },
     {
-      "name": "olko:fill-music-player",
-      "source": "./packages/music/fill-music-player/adapters/grok",
-      "description": "Fill a portable music player with a curated random selection from a source music library while balancing formats, artists, albums, and capacity."
+      "name": "olko-apple-kit",
+      "source": "./adapters/grok/olko-apple-kit",
+      "description": "Build and ship Apple platform apps: macOS menubar apps, App Store submissions."
     },
     {
-      "name": "olko:product-builder",
-      "source": "./packages/software-development/product-builder/adapters/grok",
-      "description": "Build a full-stack web application or SaaS product from a user description using production-oriented defaults."
+      "name": "olko-garmin-kit",
+      "source": "./adapters/grok/olko-garmin-kit",
+      "description": "Build, test and publish Garmin Connect IQ watch faces."
     },
     {
-      "name": "olko:mvp-oneshot",
-      "source": "./packages/software-development/mvp-oneshot/adapters/grok",
-      "description": "Turn a rough product idea into a shippable one-week MVP in one pass via a four-role prompt chain: scope a build prompt, ruthlessly trim it, plan the build, and self-review the vertical slice."
+      "name": "olko-creative",
+      "source": "./adapters/grok/olko-creative",
+      "description": "Creative and personal projects: photo galleries, music players, listings, wiki editing."
     },
     {
-      "name": "olko:starter-rules",
-      "source": "./packages/software-development/starter-rules/adapters/grok",
-      "description": "Load and enforce hard rules for every oleg-koval/* starter: 300-line files, E2E tests, pre-commit hooks, Vertical Slice architecture, no comments, KISS/DRY/SOLID."
-    },
-    {
-      "name": "olko:review-past-performance",
-      "source": "./packages/software-development/review-past-performance/adapters/grok",
-      "description": "Self-improvement loop that pulls the last 24h of ICM memories, git history, and skill analytics to detect repeated mistakes, slow workflows, and missing coverage, then proposes 1-3 concrete improvements."
-    },
-    {
-      "name": "olko:relay",
-      "source": "./packages/software-development/relay/adapters/grok",
-      "description": "Use claude-relay to run long or rate-limit-prone tasks autonomously across subscription accounts."
-    },
-    {
-      "name": "olko:open-source-publisher",
-      "source": "./packages/software-development/open-source-publisher/adapters/grok",
-      "description": "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, optional donation setup, and optional motion previews for generated static images."
-    },
-    {
-      "name": "olko:viral-launch",
-      "source": "./packages/marketing/viral-launch/adapters/grok",
-      "description": "Set up a project repository and launch plan for shareable marketing, public launch readiness, and growth loops."
-    },
-    {
-      "name": "olko:search-console-indexing-audit",
-      "source": "./packages/marketing/search-console-indexing-audit/adapters/grok",
-      "description": "Analyze Google Search Console Coverage CSV exports and correlate them with sitemap, robots, canonical, redirect, and noindex signals."
-    },
-    {
-      "name": "olko:website-analytics-bootstrap",
-      "source": "./packages/marketing/website-analytics-bootstrap/adapters/grok",
-      "description": "Set up a website's first SEO analytics loop with persistent SerpBear rank tracking, Google Search Console, seeded keywords, read-only technical audits, and Telegram alerts on a local host or NAS."
-    },
-    {
-      "name": "olko:cloudflare-block-countries",
-      "source": "./packages/software-development/cloudflare-block-countries/adapters/grok",
-      "description": "Block specific countries via Cloudflare WAF Custom Rules using the Cloudflare API. Handles creating new rulesets and updating existing ones across single or multiple zones."
-    },
-    {
-      "name": "olko:obsidian-pr-sync",
-      "source": "./packages/software-development/obsidian-pr-sync/adapters/grok",
-      "description": "Fetch open GitHub PRs assigned to you or requesting your review, and write a grouped, age-sorted '## PRs to review' section into today's Obsidian daily note. Idempotent — re-running replaces the section."
-    },
-    {
-      "name": "olko:obsidian-task-rollover",
-      "source": "./packages/software-development/obsidian-task-rollover/adapters/grok",
-      "description": "Bullet-journal end-of-day task migration: copy unchecked tasks from today's Obsidian daily note to the next workday's note under '## Carried over', and mark them [>] in the source. Skips weekends, idempotent."
-    },
-    {
-      "name": "olko:apple-store-submit",
-      "source": "./packages/software-development/apple-store-submit/adapters/grok",
-      "description": "Handle Apple App Store rejection emails end-to-end: parse rejection reasons, plan fixes, implement code changes, navigate App Store Connect, and resubmit."
-    },
-    {
-      "name": "olko:macos-menubar-app",
-      "source": "./packages/software-development/macos-menubar-app/adapters/grok",
-      "description": "Build a production-quality macOS menubar or notch app in SwiftUI — MenuBarExtra, sandbox entitlements, keyboard shortcuts, sound effects, accessibility permissions, and App Store preparation."
-    },
-    {
-      "name": "olko:skill-budget-audit",
-      "source": "./packages/software-development/skill-budget-audit/adapters/grok",
-      "description": "Diagnose and fix Claude Code skill context budget overflow — identify heavy plugin bundles, remove domain-specific ones, and restore skill discoverability."
-    },
-    {
-      "name": "olko:crash-course",
-      "source": "./packages/software-development/crash-course/adapters/grok",
-      "description": "Expert tutor for rapid, source-grounded learning of any topic: a timed 4-hour sprint plus cheat-sheet, learning-ladder, quiz-me, Feynman, and resource-curation modes."
-    },
-    {
-      "name": "olko:pr-finalize",
-      "source": "./packages/software-development/pr-finalize/adapters/grok",
-      "description": "Drives one GitHub PR to genuinely merge-ready: rebases and resolves conflicts, sweeps every review bot and human comment to zero unaddressed findings, verifies unit and E2E coverage actually exists, runs the repo's real lint/format/test gates before pushing, and reports what still needs a human."
-    },
-    {
-      "name": "olko:pr-finalize-complete",
-      "source": "./packages/software-development/pr-finalize-complete/adapters/grok",
-      "description": "Confirms a PR is genuinely merge-ready when the work is already believed done: re-checks every review-bot and human finding against the current code, separates stale comments from fixed ones, runs the repo's real lint and test gates, and reports the evidence rather than the assumption."
-    },
-    {
-      "name": "olko:qodoloop",
-      "source": "./packages/software-development/qodoloop/adapters/grok",
-      "description": "Iteratively drives a GitHub PR to zero unresolved Qodo findings — reads each finding's own Agent Prompt, applies the fix, replies to the thread, resolves it, pushes, and waits for Qodo's next pass."
-    },
-    {
-      "name": "olko:garmin-watchface",
-      "source": "./packages/wearables/garmin-watchface/adapters/grok",
-      "description": "Design, build, test, screenshot and publish Garmin Connect IQ watch faces in Monkey C."
-    },
-    {
-      "name": "olko:coderabbitloop",
-      "source": "./packages/software-development/coderabbitloop/adapters/grok",
-      "description": "Iteratively drives a GitHub PR to zero unresolved CodeRabbit findings — reads each inline comment's own Prompt for AI Agents block, applies the fix, replies to the thread, resolves it, pushes, and re-triggers CodeRabbit."
-    },
-    {
-      "name": "olko:codexloop",
-      "source": "./packages/software-development/codexloop/adapters/grok",
-      "description": "Iteratively drives a GitHub PR to zero unresolved OpenAI Codex review comments — but verifies every finding against the real code first, fixes only the correct ones, and rebuts false positives without changing correct code."
-    },
-    {
-      "name": "olko:geminiloop",
-      "source": "./packages/software-development/geminiloop/adapters/grok",
-      "description": "Iteratively drives a GitHub PR to zero unresolved Gemini Code Assist comments — treats each one as a claim to verify, fixes only the genuinely-correct findings, and rebuts the rest with evidence instead of editing correct code."
-    },
-    {
-      "name": "olko:add-to-my-skills",
-      "source": "./packages/software-development/add-to-my-skills/adapters/grok",
-      "description": "Copy a newly created skill from another repo into this catalog, refresh the README and generated manifests, then commit and push."
-    },
-    {
-      "name": "olko:wrap-up",
-      "source": "./packages/software-development/wrap-up/adapters/grok",
-      "description": "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches."
-    },
-    {
-      "name": "olko:ai-tools-setup",
-      "source": "./packages/software-development/ai-tools-setup/adapters/grok",
-      "description": "Set up, repair, and report on the RTK+ICM+Vox AI development toolkit, including hooks and MCP configuration."
-    },
-    {
-      "name": "olko:changelog-generator",
-      "source": "./packages/software-development/changelog-generator/adapters/grok",
-      "description": "Create user-facing changelogs from git history by categorising commits and rewriting them for readers rather than developers."
-    },
-    {
-      "name": "olko:wikipedia-uk-editor",
-      "source": "./packages/software-development/wikipedia-uk-editor/adapters/grok",
-      "description": "Draft policy-compliant Ukrainian Wikipedia edits — translate an English article into uk, expand or source an existing uk article, or fix a maintenance backlog item — and return ready-to-paste wikitext plus an edit summary."
-    },
-    {
-      "name": "olko:pr-description-writer",
-      "source": "./packages/software-development/pr-description-writer/adapters/grok",
-      "description": "Draft and post a GitHub PR title and body from git diff and commit history. Chains after git-commit and before qodoloop / coderabbitloop."
-    },
-    {
-      "name": "olko:ci-fix-loop",
-      "source": "./packages/software-development/ci-fix-loop/adapters/grok",
-      "description": "Diagnose GitHub Actions CI failures in a loop: fetch failing check logs, fix, push, and repeat until green. Direct analog of qodoloop / coderabbitloop for test and lint failures."
-    },
-    {
-      "name": "olko:pr-to-green",
-      "source": "./packages/software-development/pr-to-green/adapters/grok",
-      "description": "Orchestrate a GitHub PR from first push to merge-ready: run ci-fix-loop until checks are green, detect active AI review bots, run qodoloop and coderabbitloop in sequence, and confirm zero unresolved threads."
-    },
-    {
-      "name": "olko:dependabot-triage",
-      "source": "./packages/software-development/dependabot-triage/adapters/grok",
-      "description": "Triage open Dependabot and Renovate PRs in bulk: classify by risk tier, auto-approve and merge safe patch bumps, flag breaking major upgrades for human review, and post a digest."
-    },
-    {
-      "name": "olko:store-listing-copy",
-      "source": "./packages/software-development/store-listing-copy/adapters/grok",
-      "description": "Generate platform-validated App Store, Google Play, and Connect IQ store listing copy (title, subtitle, description, what's new, keywords) from a git changelog or release notes."
-    },
-    {
-      "name": "olko:pr-finalize-complete",
-      "source": "./packages/software-development/pr-finalize-complete/adapters/grok",
-      "description": "Comprehensive PR finalization workflow for PRs that may already be partially addressed: checks each review comment's actual current status in code, distinguishes fixed vs. stale vs. still-present findings, verifies test coverage, runs real lint/test gates, and reports what still needs a human."
-    },
-    {
-      "name": "olko:morning-routine",
-      "source": "./packages/software-development/morning-routine/adapters/grok",
-      "description": "Run the complete start-of-day setup in one pass: roll over unfinished Obsidian tasks to today's daily note, sync open GitHub PRs that need your attention, and sweep Dependabot patch bumps. Chains obsidian-task-rollover, obsidian-pr-sync, and dependabot-triage."
-    },
-    {
-      "name": "olko:release-day",
-      "source": "./packages/software-development/release-day/adapters/grok",
-      "description": "Orchestrate a full release-day workflow for iOS, Android, or Garmin apps: verify main branch CI is green, generate changelog, draft platform-ready store listing copy, trigger semantic-release or tag manually, wait for the build, and queue the App Store submission."
-    },
-    {
-      "name": "olko:branch-cleanup",
-      "source": "./packages/software-development/branch-cleanup/adapters/grok",
-      "description": "Prune stale git branches after a merge wave: delete closed/merged remote branches, remove local tracking refs that no longer exist on the remote, and optionally clean up merged local branches. Natural follow-up to dependabot-triage."
-    },
-    {
-      "name": "olko:vinted-listing",
-      "source": "./packages/software-development/vinted-listing/adapters/grok",
-      "description": "Create, edit, and safely publish Vinted listings through the signed-in browser, using verified item details and the owner’s original photos."
+      "name": "olko-web-ops",
+      "source": "./adapters/grok/olko-web-ops",
+      "description": "Operate a website: WAF rules, search console audits, analytics bootstrap, docs indexes."
     }
   ]
 }

package/.kiro/steering/retro-analysis.md

@@ -0,0 +1,204 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+inclusion: manual
+description: "Produce repository, comparison, and cross-project engineering retrospectives from delivery, code-quality, work-pattern, and trend evidence."
+---
+
+# Retro Analysis
+
+Run a factual engineering retrospective over a defined time window. The purpose is to explain what changed, how the work happened, what quality signals say, what was learned, and what should improve next. This is an analysis workflow, not a performance-ranking or blame exercise.
+
+Use it manually at the end of a day, week, sprint, or release; on a recurring schedule; or when asked what was shipped, where time went, or how delivery quality is trending. When a specific implementation has just reached its goal, run this analysis before or alongside `olko:wrap-up` so the delivery audit and the broader retrospective remain distinct.
+
+## Invocation
+
+Accept one of these arguments:
+
+- no argument or `7d`: the previous seven calendar days
+- `24h`: the previous 24 hours
+- `14d` or `30d`: the previous N calendar days
+- `compare` or `compare 14d`: compare the selected window with the immediately preceding window of equal length
+- `global`, `global 14d`: aggregate across discoverable repositories and agent sessions
+
+If the argument is invalid, print the accepted forms and stop. Do not silently choose a different window.
+
+Calendar windows are aligned to midnight in the operator's local timezone. A short hourly window may use a relative timestamp. State the resolved start, end, timezone, scope, and comparison window at the beginning of the report.
+
+## Safety and evidence rules
+
+- Be read-only by default. Do not push, merge, deploy, close issues, edit source, or rewrite history.
+- A local retro may write one task-owned snapshot under `.context/retros/` when that directory exists or when persistence is explicitly requested. Never overwrite an existing snapshot; use a date and window-specific filename.
+- Do not fetch or refresh remote refs unless the user or the surrounding workflow authorized that read-side state change. If refs may be stale, say so and use the available evidence.
+- Preserve dirty work, untracked files, existing snapshots, credentials, and unrelated temporary artifacts.
+- Never infer delivery from a local commit. Treat local Git, remote/PR state, CI, deployment, and device or human QA as separate evidence gates.
+- Do not expose secrets, tokens, private prompts, or raw session content. Use aggregate counts and redacted references only.
+- Missing data is `UNKNOWN`, not zero. Distinguish “none found” from “not available”.
+- Do not turn commit count, lines changed, hours, or AI-assisted activity into a simplistic productivity score. Use them as context for the narrative.
+
+## 1. Establish scope and baseline
+
+For repository mode:
+
+1. Identify the repository, current branch, `HEAD`, configured author, base branch, and working-tree state.
+2. Preserve and report pre-existing dirty paths; do not include their changes as delivered work unless the evidence links them to the window.
+3. Use the repository's local timezone for calendar boundaries. Use UTC timestamps in stored machine-readable data.
+4. Read only relevant project documentation and task artifacts needed to interpret the changes. Do not invent milestones, objectives, or acceptance criteria.
+5. Locate prior snapshots in `.context/retros/` and load the immediately preceding comparable snapshot when available.
+
+For global mode:
+
+1. Discover repositories from the configured workspace locations or an existing discovery tool. If discovery is unavailable, report that limitation and continue with explicitly supplied paths.
+2. For each repository, collect the same bounded evidence as repository mode and skip missing, inaccessible, or non-Git directories.
+3. Optionally include available agent/session summaries or tool telemetry, but only as aggregate, redacted evidence. Do not require a specific agent vendor, plugin, or telemetry format.
+4. Keep per-project results separate before producing cross-project totals. Never hide a repository-level failure in an aggregate.
+
+## 2. Collect raw evidence
+
+Capture enough raw data to reproduce the analysis. Prefer stable Git/provider CLIs already present in the environment. Save only the normalized snapshot unless raw artifacts were explicitly requested.
+
+### Repository history
+
+Collect, bounded to the resolved window and scope:
+
+- commit hash, author, timestamp, subject, body, and parent information
+- insertions, deletions, files changed, and test-file versus production-file changes
+- commit type signals from Conventional Commit prefixes, labels, or equivalent repository conventions
+- pull request or merge request references present in commits, and provider state when a provider CLI is available
+- changed-file frequency, churn, and hotspots; distinguish generated, vendored, lockfile, and source files when possible
+- per-author commit and file ownership signals, including co-authors and AI-assisted markers only when explicitly present
+
+Use `git log --shortstat` or equivalent for commit-level change counts and `git diff --numstat` or equivalent for test/source proportions. If a command cannot run, record the command and reason; do not substitute invented values.
+
+### Delivery and quality signals
+
+Inspect only signals that exist in the repository or authorized provider tooling:
+
+- branch and remote tracking state, current PR title/body, review state, and current-head checks
+- test files, test commands, recent test-related commits, and known failing or skipped checks
+- changelog, release notes, issue/task references, and plan artifacts when present
+- TODO/backlog markers when a project-maintained backlog exists
+- regression fixes, reverted changes, follow-up fixes, and repeated failure patterns
+- optional review or static-analysis summaries, clearly labeling unavailable or rate-limited providers
+
+Never call an absent test suite “healthy”; report `NOT_AVAILABLE`. Never call a skipped check green.
+
+### Work-pattern signals
+
+When timestamps are available:
+
+- build an hour-of-day histogram in local time
+- group commits or activity into sessions separated by at least 45 minutes of inactivity
+- classify sessions as deep (3+ hours), medium (1–3 hours), or micro (<1 hour)
+- count active days, longest streak, and context switches between repositories or work areas
+
+Treat commit timestamps as a proxy, not proof of keyboard time. If session telemetry exists, prefer it and name the source.
+
+## 3. Compute the analysis
+
+Use the evidence to calculate, or explicitly mark unavailable, the following dimensions:
+
+### Shipping and scope
+
+- features, fixes, refactors, docs, tests, chores, and releases shipped
+- commits, weighted commits, active days, contributors, and referenced PRs
+- version range or release identifiers when the repository exposes them
+- logical lines changed and raw lines changed, reported separately
+- plan or objective items completed, deferred, or still open when a plan is available
+
+### Quality and maintainability
+
+- test lines or test files changed relative to production changes
+- test commands run and their current result
+- regressions, reverts, repeated fixes, and hotspots with high churn
+- type, lint, build, security, review, and release signals when available
+- backlog/TODO health only when there is a maintained source to inspect
+
+Do not reward large diffs or penalize small ones without explaining their context. A small change that closes a high-value objective can be the most important shipment.
+
+### Focus and delivery flow
+
+- commit-type mix and fix ratio; flag a high fix ratio as a signal for investigation, not a diagnosis
+- PR/MR size buckets and time-to-merge when provider data is available
+- work sessions, time-of-day distribution, context switching, and focus patterns
+- planned versus unplanned work, if the plan and change evidence support the comparison
+- the single most consequential shipment or decision, with evidence and caveats
+
+### People and collaboration
+
+For multi-author work, provide a factual per-author view of commits, change volume, areas touched, review or PR participation, and notable contributions. Include a team view of ownership concentration, cross-review, handoffs, and shared hotspots. Avoid ranking people by raw LOC or commit count.
+
+Use the configured Git author as the personal focus only when it is unambiguous. Otherwise produce a team report and state that no personal identity was selected.
+
+## 4. Compare and track trends
+
+For `compare` or any window with a prior snapshot:
+
+- compare features/fixes, commits, active days, contributors, PRs, change volume, test signals, regressions, and backlog movement
+- identify meaningful directional changes and explain whether the evidence is strong, weak, or incomplete
+- preserve the same metric definitions between periods; do not compare a repository window to a global window as if they were equivalent
+- report streaks, recurring hotspots, repeated failure modes, and unresolved improvements only when snapshots support them
+
+Store a JSON snapshot with stable keys, UTC timestamps, resolved window, scope, repository identity, commit/PR identifiers, metric values, evidence limitations, and a short list of findings. Keep narrative prose out of fields intended for machine comparison. A snapshot is an aid to future analysis, not a source of truth that overrides current evidence.
+
+## 5. Optionally promote durable lessons
+
+This phase is opt-in. A retrospective remains read-only unless the user or the surrounding workflow explicitly requests promotion to the shared ledger. Do not silently turn analysis into a write operation.
+
+Before adding any finding:
+
+1. Locate and read the current shared ledger. When a Git-backed repository ledger exists, read that repository file directly and treat it as authoritative. If it is absent or inaccessible, report `NOT_AVAILABLE` and do not claim that the ledger was checked.
+2. Classify the finding as one of:
+   - `local action` — a project- or task-specific follow-up that belongs in the report or backlog, not the shared ledger.
+   - `lesson` — a durable practice that generalizes across projects.
+   - `trap` — a non-obvious failure mode that can silently produce incorrect work.
+   - `preference` — a stable way the operator wants agents to work.
+3. Promote only non-obvious, durable, cross-project lessons, traps, or preferences. Keep local actions in the retrospective or project task system.
+4. Attach evidence to every promoted finding: a source path, commit, check, or other redacted reference, or the concrete failure that caused the rule. Do not promote an unsupported impression.
+5. Do not duplicate existing project instructions, shared-ledger notes, or behavior already enforced by an automated check. A thin ledger is more useful than a repetitive one.
+
+When promotion is authorized, append new notes using the current ledger schema; never rewrite, reorder, or overwrite existing entries. If no note is justified, append nothing. Report each added note ID, or `NOT_WRITTEN` when no note was added, promotion was not requested, or the ledger could not be safely updated.
+
+## 6. Produce the report
+
+Lead with a concise, shareable summary of the period. Then use this order:
+
+1. **Scope and evidence** — window, timezone, repositories, branch/base, sources, and limitations.
+2. **Summary table** — shipping, activity, quality, and delivery metrics with `UNKNOWN` where needed.
+3. **What shipped** — the most important features, fixes, releases, or decisions, tied to commits/PRs.
+4. **Trends** — comparison with the previous period, if available.
+5. **Time and sessions** — active days, session shape, time distribution, and context switching.
+6. **Quality and test health** — checks, regressions, churn hotspots, review signals, and open risks.
+7. **Plan completion** — objective items completed, deferred, or missing evidence.
+8. **Focus and collaboration** — personal or team analysis with fair context.
+9. **Top wins** — three evidence-backed wins when enough evidence exists.
+10. **Improvements** — three concrete, small, actionable improvements; fewer is fine when evidence is limited.
+11. **Next-period habits** — explicit habits or experiments with an owner or trigger when known.
+12. **Limitations** — missing refs, unavailable provider data, stale telemetry, dirty work, or ambiguous attribution.
+
+Use compact tables for exact metrics and prose for interpretation. Label inference as inference. Link or name evidence paths/commit IDs where useful, but never paste private content.
+
+## 7. End-of-task handoff
+
+If this run is explicitly closing a completed implementation, continue with `olko:wrap-up`:
+
+- use the retro to check that the delivered work matches the original idea and to capture follow-up items
+- let `wrap-up` perform the separate local/remote/PR/CI/deployment/QA gates and task-owned cleanup
+- preserve the retro snapshot and report any limitation instead of deleting evidence
+
+For a periodic or global retrospective, do not clean worktrees, branches, logs, or temporary files unless the user explicitly asks for that separate cleanup. Analysis alone must not alter delivery state.
+
+## Minimal final status
+
+End every run with:
+
+```text
+RETRO_STATUS: DONE | DONE_WITH_LIMITATIONS | BLOCKED
+WINDOW: <resolved window and timezone>
+SCOPE: <repository or repositories>
+SNAPSHOT: <path, NOT_WRITTEN, or NOT_AVAILABLE>
+TOP_FINDINGS: <short summary>
+NEXT_ACTIONS: <short actionable list>
+```
+
+Use `BLOCKED` only when the requested scope cannot be analyzed safely or the required evidence is inaccessible. A partial but clearly labeled report is `DONE_WITH_LIMITATIONS`.

package/.kiro/steering/wrap-up.md

@@ -57,20 +57,40 @@ Clean only paths created by this task or explicitly named for cleanup.
 
 ## 6. Report the result
 
-Lead with the outcome. Include concise evidence, cleanup performed, items intentionally preserved, and the smallest next action for any blocker. Always finish with this receipt, using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable checks that were not executed:
+Lead with the outcome. Use a short `DELIVERY RECEIPT` heading and a one- or
+two-sentence summary before the fields. Add `STATUS`, `NEXT_PHASE`, and
+`NEXT_STEP` near the top when follow-up work remains. Keep the required fields
+flush-left and grouped with one blank line between logical groups, not between
+every field. Keep each value concise and avoid repeating the same prose. Do
+not use Markdown tables, decorative separators, bullets, emojis, or indented
+continuation lines inside the canonical field block. Put `FINAL_STATUS` last.
+Add `LOCAL_COMMIT` when a local commit exists. Always finish with this receipt,
+using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable
+checks that were not executed:
 
 ```text
+DELIVERY RECEIPT
+
+<short outcome summary>
+STATUS: <DELIVERED | BLOCKED | INTENTIONALLY_UNCHANGED>
+NEXT_PHASE: <next phase or NOT_APPLICABLE>
+NEXT_STEP: <single smallest next action or NOT_APPLICABLE>
+
 OBJECTIVE:
 CHANGED:
 NOT_CHANGED:
+
 TESTS:
 BUILD:
+
 REMOTE:
 PR:
 CI:
 DEPLOYMENT:
 DEVICE_OR_HUMAN_QA:
+
 KNOWN_LIMITATIONS:
+LOCAL_COMMIT: <hash and subject, or NOT_APPLICABLE>
 FINAL_STATUS:
 ```