Convex Create Component
spokvulcan/poker-planning
Builds reusable Convex components with isolated tables and app-facing APIs.
Draft a Sprint Retro by synthesizing scrum dailies, recaps, the sprint planning note, and the prior retro.
Install Sprint Retro
$ npx skills add benoror/obsidianos_work --skill sprint-retro -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install benoror/obsidianos_work sprint-retro --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/benoror/obsidianos_work.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/sprint-retro .claude/skills/sprint-retro && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sprint-retro" agent skill from https://github.com/benoror/obsidianos_work/tree/main/.agents/skills/sprint-retro into .claude/skills/sprint-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/benoror/obsidianos_work/tree/main/.agents/skills/sprint-retroType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add benoror/obsidianos_work --skill sprint-retro -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install benoror/obsidianos_work sprint-retro --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/benoror/obsidianos_work.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/sprint-retro .agents/skills/sprint-retro && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sprint-retro" agent skill from https://github.com/benoror/obsidianos_work/tree/main/.agents/skills/sprint-retro into .agents/skills/sprint-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add benoror/obsidianos_work --skill sprint-retro -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install benoror/obsidianos_work sprint-retro --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/benoror/obsidianos_work.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/sprint-retro .cursor/skills/sprint-retro && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sprint-retro" agent skill from https://github.com/benoror/obsidianos_work/tree/main/.agents/skills/sprint-retro into .cursor/skills/sprint-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/benoror/obsidianos_work.git --path .agents/skills/sprint-retro--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add benoror/obsidianos_work --skill sprint-retro -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install benoror/obsidianos_work sprint-retro --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/benoror/obsidianos_work.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/sprint-retro .gemini/skills/sprint-retro && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sprint-retro" agent skill from https://github.com/benoror/obsidianos_work/tree/main/.agents/skills/sprint-retro into .gemini/skills/sprint-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install benoror/obsidianos_work sprint-retroInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add benoror/obsidianos_work --skill sprint-retro -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/benoror/obsidianos_work.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/sprint-retro .github/skills/sprint-retro && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sprint-retro" agent skill from https://github.com/benoror/obsidianos_work/tree/main/.agents/skills/sprint-retro into .github/skills/sprint-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add benoror/obsidianos_work --skill sprint-retro -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install benoror/obsidianos_work sprint-retro --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/benoror/obsidianos_work.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/sprint-retro .opencode/skills/sprint-retro && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sprint-retro" agent skill from https://github.com/benoror/obsidianos_work/tree/main/.agents/skills/sprint-retro into .opencode/skills/sprint-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sprint-retro", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sprint-retro- GitHub stars
- 165
- Token cost
- ~1.9k tokens
- SKILL.md length
- 745 words
- Files
- 1
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Draft a Sprint Retro by synthesizing scrum dailies, recaps, the sprint planning note, and the prior retro.
- Works in 7 steps: Determine sprint number and window → Gather sources → Synthesize → …
- Tasks that involve Sprint planning and agile
- SKILL.md covers Usage, Output format (mandatory), File naming convention… and Workflow, plus 1 more section
- Calls git
What it does
Sprint Retro is an agent skill from benoror/obsidianos_work. Draft a Sprint Retro by synthesizing scrum dailies, recaps, the sprint planning note, and the prior retro. Args: [sprint number | dates]. No args = infer the current sprint.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires qmd (CLI or MCP) for vault search. Reads recaps, scrum dailies, and the Tracker.
It sits in Product & Project Management, covering Sprint planning and agile. The repository describes itself as: ObsidianOS - Work Vault. The licence is MIT.
When your agent uses it
- Tasks that involve Sprint planning and agile
Example prompts
- “/sprint-retro”
Requirements
- Compatibility (from SKILL.md): Requires qmd (CLI or MCP) for vault search. Reads recaps, scrum dailies, and the Tracker.
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3c7923e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires qmd (CLI or MCP) for vault search. Reads recaps, scrum dailies, and the Tracker.
From compatibility in the SKILL.md frontmatter.
Context cost
Sprint Retro loads about 1.9k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 745 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from benoror/obsidianos_work at commit 3c7923e, republished under its MIT licence (© benoror). 745 words, ~1,869 tokens.
Download SKILL.mdSave it as
.claude/skills/sprint-retro/SKILL.md (or your agent's skills folder).- name
- sprint-retro
- description
- Draft a Sprint Retro by synthesizing scrum dailies, recaps, the sprint planning note, and the prior retro. Args: [sprint number | dates]. No args = infer the current sprint.
- compatibility
- Requires qmd (CLI or MCP) for vault search. Reads recaps, scrum dailies, and the Tracker.
- license
- MIT
Sprint Retro
Synthesize a draft Sprint Retro from everything already in the vault — daily standups, weekly recaps, the sprint planning note, and the previous retro — so the live retro starts from a populated document instead of a blank template.
Usage
/sprint-retro— Infer the current/most-recent sprint from the prior retro + cadence./sprint-retro <N>— Draft the retro for sprint numberN./sprint-retro <dates>— Use an explicit sprint window (e.g.2026-05-19..2026-06-02).
Date Filtering
See date-filter for date-range syntax and parsing.
Output format (mandatory)
Mirror followup-todos — the retro is a bullet document, not a task list:
- Never insert Obsidian Tasks / checkbox lines: no
- [ ],- [x],- [-],- [?]— including in the Action items section. - Never append Tasks date tokens (
📅,🛫,⏳). Write dates inline in prose / ISO (e.g. "by 2026-06-01"). - A single trailing priority emoji (
🔺⏫🔼🔽) as plain text is fine when it reads naturally. - Always use plain list items:
- Description…. Wikilinks ([[@Name]],[[Recap …]]),[PROJ-123](https://…)links, and bold are encouraged.
File naming convention (mandatory)
Sprint artifacts in Meetings/Engineering/Scrum/ follow a single pattern — keep it consistent:
- Retro:
Sprint <N> Retro <YYYY-MM-DD>.md(date = sprint end date / retro day). - Planning:
Sprint <N> Planning <YYYY-MM-DD>.md(date = planning meeting day).
Never leave an undated Sprint N Retro.md or a <Team> - Sprint Planning … variant. If you encounter one while gathering context, flag it and offer to git mv it into the canonical form (updating any [[wikilinks]] that reference the old name).
Workflow
Step 1: Determine sprint number and window
- Verify the current date (see Date Verification in skill-conventions):
date +%F. - List
Meetings/Engineering/Scrum/Sprint * Retro *.mdto find the prior retro (Sprint <N-1> Retro <date>). - Derive this sprint:
- Number = prior + 1 (or the explicit
<N>arg). - Window = the day after the prior retro's end through this sprint's retro day. Retros land on a biweekly cadence (same weekday, ~14 days apart) — extrapolate, then sanity-check against the planning note's date and the scrum dailies present.
- Number = prior + 1 (or the explicit
- Confirm the resolved sprint number and
start..endwindow with the user if anything is ambiguous (missing prior retro, irregular cadence, mid-sprint run).
Step 2: Gather sources
See vault-context. Gather in parallel:
| Source | Where | What to extract |
|---|---|---|
| Scrum dailies | Meetings/Engineering/Scrum/YYYY-MM-DD.md within the window | Yesterday/Today/Blockers, ticket IDs, merges, incidents, decisions |
| Recaps | Recaps/Recap *.md whose period: overlaps the window | Highlights, decisions, open items, insights, cross-team notes |
| Sprint planning | Sprint <N> Planning <date>.md | Committed tickets, estimates, decisions — to measure against outcomes |
| Prior retro | Sprint <N-1> Retro <date>.md | Open Action items to carry forward and check off |
| Tracker | Tracker.md | Current ticket status (Done / Blocked / Paused / WIP) |
Prefer qmd over grep for discovery (see qmd). Resolve names to [[@Name]] via people-resolver.
Show full SKILL.md (322 more words)Show less
Step 3: Synthesize
Distill the gathered material into the retro sections, attributing each bullet to its source(s) with wikilinks (e.g. ([[Recap 2026-05-31]], [[Meetings/Engineering/Scrum/2026-05-28]])). Enrich bullets with Jira links ([PROJ-1234](https://your-org.atlassian.net/browse/PROJ-1234)) where a ticket is referenced.
- Went Well / Start doing — shipped tickets, milestones, unblocks, demos.
- Didn't Go Well / Stop doing — misses, recurring blockers, process friction, deadline pressure. Note cross-sprint patterns.
- Keep doing / Shoutouts — one bullet per person, citing their concrete contributions. Only include people with evidence in the sources; don't invent contributions.
- Discussion/Proposals — open questions, decisions to make, timelines.
- Action items — concrete next steps (plain bullets, see output rules), including carried-over items from the prior retro.
Step 4: Compose the document
Base structure on Templates/Sprint Retro.md, with these additions used by recent retros:
---
Notes:
created: YYYY-MM-DDTHH:MM:SS±HH:MM
Participants: "[[+Engineering]]"
---
# Sprint <N> Retro — <YYYY-MM-DD>
**Sprint:** <N> · **<start>** → **<end>**
Planning context: [[Sprint <N> Planning <date>]]
> [!info] Draft synthesized from the vault
> Bullets below are distilled from **Scrum dailies** (`<start>`–`<end>`), the recaps covering this window, and the **[[Sprint <N> Planning <date>]]** commitments. Adjust after the live retro or paste a Confluence URL into `Notes:`.
### ▶️ Start doing / Went Well
- …
### 🛑 Stop doing / Didn't Go Well
- …
### 🙌 Keep doing / Shoutouts
- **[[@Name]]** — …
## Discussion/Proposals
- …
## Action items
- … 🔼
- Carry: … ⏫
## Sources (vault index)
| Kind | Notes |
| --- | --- |
| Recaps | [[Recap …]] (range), [[Recap …]] (range) |
| Scrum DS | [[Meetings/Engineering/Scrum/<start>]] … [[Meetings/Engineering/Scrum/<end>]] |
| Grooming / forums | [[Sprint <N> Planning <date>]] |
| Prior retro | [[Sprint <N-1> Retro <date>]] |Leave Notes: empty for the user to paste the Confluence retro URL. Never set modified: manually (Obsidian manages it).
Step 5: Present and confirm
Show the draft to the user before saving. Let them adjust bullets, attributions, shoutouts, and action items.
Step 6: Save
Save to Meetings/Engineering/Scrum/Sprint <N> Retro <end-date>.md — see the naming convention above. If a retro for the sprint already exists, ask whether to overwrite.
Step 7: Offer to commit
See /commit.
Important Notes
- Draft, not gospel — the output is a synthesis to seed the live retro; flag it as such in the
[!info]callout and expect the user to revise. - Evidence-only shoutouts — only credit contributions that appear in the sources; omit team members with no traceable activity rather than guessing.
- Cadence is a heuristic — biweekly same-weekday is the norm, but planning/retro days drift; always cross-check the derived window against the actual scrum dailies and planning-note date.
- Naming consistency — if you touch sibling planning/retro files with non-canonical names, normalize them via
git mvand fix referencing wikilinks (see the convention section). - No checkboxes — this is a discussion artifact; keep it bullets-only per the output rules, matching
/followup-todos. - Timezone — use the vault owner's offset from USER.md. See skill-conventions Project Context.
© benoror, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/sprint-retro of benoror/obsidianos_work.
Open the folder on GitHubat commit 3c7923e
Compare with similar skills
Sprint Retro next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sprint Retro this skillbenoror/obsidianos_work | 165 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Convex Create Componentspokvulcan/poker-planning | 114 | 8 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Convex Migration Helperspokvulcan/poker-planning | 114 | 8 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Convex Performance Auditspokvulcan/poker-planning | 114 | 7 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Walking Skeleton Roadmap Scopingprime-radiant-inc/iterative-development | 181 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Convex Migration Helper
spokvulcan/poker-planning
Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations.
Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Convex Performance Audit
spokvulcan/poker-planning
Audits Convex performance for reads, subscriptions, write contention, and function limits.
Walking Skeleton Roadmap Scoping
prime-radiant-inc/iterative-development
Turns extracted requirements into a roadmap by choosing a walking skeleton iteration with its first journey scenario and ordering the remaining work into follow-on iterations.
Convex
spokvulcan/poker-planning
Routes general Convex requests to the right project skill. An agent skill from spokvulcan/poker-planning.
More from benoror/obsidianos_work
All 18 skills in this repoQmd
benoror/obsidianos_work
Search vault notes by keyword or meaning. An agent skill from benoror/obsidianos_work.
Cache Notes
benoror/obsidianos_work
Fetch & embed AI transcripts as Obsidian callouts. An agent skill from benoror/obsidianos_work.
Fill Participants
benoror/obsidianos_work
Resolve and fill Participants frontmatter + link unlinked names in body.
Followup Todos
benoror/obsidianos_work
Extract action items as plain markdown bullets (with confirmation).
Last 1on1
benoror/obsidianos_work
Show when you last had a 1:1 with each direct report / peer, sorted by recency.
Mail Transcripts
benoror/obsidianos_work
Gmail AI transcript notifications → meeting Notes: URLs + mark read.
Related
Categories
Questions about Sprint Retro
What does Sprint Retro do?
Draft a Sprint Retro by synthesizing scrum dailies, recaps, the sprint planning note, and the prior retro. Sprint Retro is an agent skill from benoror/obsidianos_work. Draft a Sprint Retro by synthesizing scrum dailies, recaps, the sprint planning note, and the prior retro.
When should I use Sprint Retro?
Sprint Retro fits situations like: tasks that involve Sprint planning and agile.
How do I install Sprint Retro in Claude Code?
Run `npx skills add benoror/obsidianos_work --skill sprint-retro -a claude-code`. Or copy the skill folder (.agents/skills/sprint-retro in benoror/obsidianos_work) into .claude/skills/sprint-retro in your project. Claude Code loads it when a task matches its description.
How do I install Sprint Retro in Codex?
Run `npx skills add benoror/obsidianos_work --skill sprint-retro -a codex`. Or copy the skill folder (.agents/skills/sprint-retro in benoror/obsidianos_work) into .agents/skills/sprint-retro in your project. Codex loads it when a task matches its description.
Can I use Sprint Retro in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add benoror/obsidianos_work --skill sprint-retro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sprint-retro, .gemini/skills/sprint-retro, .github/skills/sprint-retro and .opencode/skills/sprint-retro in your project.
What does Sprint Retro need to run?
Going by SKILL.md and its folder, Sprint Retro needs the command-line tools its instructions call (git). Compatibility (from SKILL.md): Requires qmd (CLI or MCP) for vault search. Reads recaps, scrum dailies, and the Tracker..
Does Sprint Retro access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Sprint Retro safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sprint Retro use?
Sprint Retro is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sprint Retro use?
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sprint Retro?
Skills that share tags, products or a category with Sprint Retro: Convex Create Component (spokvulcan/poker-planning, 114 stars), Convex Migration Helper (spokvulcan/poker-planning, 114 stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Convex Performance Audit (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sprint Retro?
benoror (a GitHub user) maintains it in benoror/obsidianos_work, which has 165 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on June 11, 2026.
Source: benoror/obsidianos_work on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.