Cairn-ai-tooling
- 8 skills
- 0 followers
- 7 hours ago last updated
- ▌ Changelog · cairn-ai-toolingUse when recording a notable change — adds a correctly-placed entry under [Unreleased] in CHANGELOG.md (Keep a Changelog format), reusing the right
- ▌ Product Item · cairn-ai-tooling bundleUse when creating or scaffolding a backlog artifact — an Epic, User Story, Task, or Implementation Plan — or when graduating a docs/roadmap.md item into a tracked artifact. Scaffolds the next-numbered file from docs/product/templates/, wires parent/child links, and adds a roadmap pointer — the same shape as /decision-record but for backlog artifacts.
- ▌ Agent Handoff · cairn-ai-toolingUse when finishing a chunk of work that another agent (or a future session) will continue — produces a structured handoff capturing goal, decisions, current state, remaining work, and blockers so the next agent can resume without re-deriving context.
- ▌ Close Out Sweep · cairn-ai-tooling bundleUse when retiring completed work from a docs/product/ backlog in one pass — archiving every shipped (Done) Epic and its whole subtree into per-type archive/ dirs, regenerating the shipped index, and pruning the roadmap. Trigger whenever someone says "close out the backlog", "archive the completed/shipped epics", "sweep the backlog", "retire the done epics", "regenerate the shipped index", or "clean up docs/product now that X shipped". It is the batch counterpart to /product-item (which creates artifacts; this graduates them out once they're Done).
- ▌ Decision Record · cairn-ai-toolingUse when recording an architecture/design decision — scaffolds the next-numbered ADR in docs/decisions/ from the project's template and cross-links it.
- ▌ Github Backlog Sync · cairn-ai-tooling bundleUse when mirroring a local product backlog (docs/product/ Epics, User Stories, Tasks, Plans created by /product-item) out to GitHub Issues, or onto a GitHub Project board — creating or updating issues, keeping status in sync, and recording the issue number back on each artifact. Trigger whenever someone says "push these to GitHub Issues", "sync the backlog to GitHub", "create issues for these tasks/epics", "put this on the GitHub Project board", "mirror docs/product to GitHub", or asks whether the backlog is big enough to move onto GitHub. The local Markdown stays the source of truth; GitHub is the mirror.
- ▌ Code Review Exchange · cairn-ai-toolingUse when one agent asks another to review code, or when an agent reviews work produced by another agent — standardizes the review request (scope, diff, concerns) and the review response (severity-tagged findings, clear verdict) so review handoffs are consistent and actionable.
- ▌ Shared Task Tracking · cairn-ai-toolingUse when multiple agents work toward a shared goal and need a single source of truth for tasks — defines where the shared task list lives, how to claim/update/complete items, and conventions that prevent double-work and dropped tasks.