aiskillstore/marketplace / skills/89jobrien/agile-ceremonies
agile-ceremonies
VerifiedAgile ceremonies and sprint management specialist. Use when running standups, retrospectives, sprint planning, or tracking sprint progress.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
| references/RETROSPECTIVE.template.md | markdown | 2.1 KB |
| references/daily-standup.template.md | markdown | 2.8 KB |
| skill-report.json | config | 12.9 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-05T11:03:48.459Z",
"slug": "89jobrien-agile-ceremonies",
"source_url": "https://github.com/89jobrien/steve/tree/main/steve/skills/agile-ceremonies",
"source_ref": "main",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "a822b723e37bb0b7f8806c5eb7de79a024a40e541325020900612e33f9a74b6d",
"tree_hash": "f92adc4cbd093537a9dcb6b394a476bc1e6cc78be417bc4b9c489db5c4c758e6",
"provenance": {
"model_effective": "codex",
"fallback_chain": [
{
"agent": "codex",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "agile-ceremonies",
"description": "Guides agile teams through daily standups, retrospectives, sprint planning, sprint progress updates, action-item capture, and team health checks.",
"summary": "Run structured agile ceremonies with reusable standup, retrospective, progress, and action-item formats.",
"icon": "📦",
"version": "1.0.2",
"author": "Joseph OBrien",
"license": "MIT",
"tags": [
"agile",
"standups",
"retrospectives",
"sprint-planning",
"team-health"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"external_commands"
],
"category": "productivity"
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "Static analysis flagged progress-related wording and markdown backticks, but context shows ceremony templates and reference links. No executable commands, network reconnaissance, data exfiltration, or prompt injection indicators were found in the reviewed files.",
"remediation": [],
"risk_factor_evidence": [
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 36,
"line_end": 36
},
{
"file": "SKILL.md",
"line_start": 37,
"line_end": 37
}
]
}
],
"static_findings": [
{
"id": "blocker:references/daily-standup.template.md:57:network-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "Network reconnaissance",
"file": "references/daily-standup.template.md",
"line_start": 57,
"line_end": 58,
"snippet": "### In Progress"
},
{
"id": "blocker:references/daily-standup.template.md:117:network-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "Network reconnaissance",
"file": "references/daily-standup.template.md",
"line_start": 117,
"line_end": 118,
"snippet": "- 🟡 In Progress"
},
{
"id": "blocker:references/daily-standup.template.md:149:network-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "Network reconnaissance",
"file": "references/daily-standup.template.md",
"line_start": 149,
"line_end": 150,
"snippet": "### Progress"
},
{
"id": "external_commands:SKILL.md:36:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 36,
"line_end": 36,
"snippet": "- `references/RETROSPECTIVE.template.md` - Sprint retrospective format"
},
{
"id": "external_commands:SKILL.md:37:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 37,
"line_end": 37,
"snippet": "- `references/DAILY_STANDUP.template.md` - Standup formats (individual, team, async)"
},
{
"id": "blocker:SKILL.md:21:network-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "Network reconnaissance",
"file": "SKILL.md",
"line_start": 21,
"line_end": 22,
"snippet": "- Tracks sprint progress"
}
],
"finding_verdicts": [
{
"id": "blocker:references/daily-standup.template.md:57:network-reconnaissance",
"verdict": "false_positive",
"confidence": 0.98,
"reason": "The cited text is a standup template heading for active work. It contains no network scan command, host discovery, port probing, or external request."
},
{
"id": "blocker:references/daily-standup.template.md:117:network-reconnaissance",
"verdict": "false_positive",
"confidence": 0.98,
"reason": "The cited text is a status legend entry for work in progress. It is not related to network reconnaissance or system discovery."
},
{
"id": "blocker:references/daily-standup.template.md:149:network-reconnaissance",
"verdict": "false_positive",
"confidence": 0.98,
"reason": "The cited text is a weekly summary progress heading. No network targets, tooling, commands, or scanning behavior are present."
},
{
"id": "external_commands:SKILL.md:36:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The backticks are markdown formatting around a reference file path. They do not invoke Ruby, a shell, or any executable command."
},
{
"id": "external_commands:SKILL.md:37:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The backticks are markdown formatting around a standup template path. There is no command execution syntax or user-controlled shell input."
},
{
"id": "blocker:SKILL.md:21:network-reconnaissance",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The cited text describes tracking sprint progress as an agile practice. It does not contain network reconnaissance instructions or suspicious operational intent."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 3,
"total_lines": 394,
"audit_model": "codex",
"audited_at": "2026-07-05T11:03:48.459Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Run Agile Ceremonies",
"value_statement": "Agile teams need concise ceremonies that keep work visible and action items clear. This skill provides standup, retrospective, sprint progress, and team health formats for Claude, Codex, and Claude Code.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"agile ceremonies",
"daily standup",
"sprint retrospective",
"sprint planning",
"sprint management",
"team health check",
"async standup"
],
"actual_capabilities": [
"Structures individual, team, and asynchronous daily standups.",
"Creates sprint progress summaries with burndown, story status, risks, and decisions.",
"Facilitates retrospectives with sprint metrics, learnings, action items, and follow-up tracking.",
"Captures blockers, owners, due dates, and required support for follow-up.",
"Documents team health signals, mood checks, recognition, and process improvements."
],
"limitations": [
"Does not connect directly to Jira, GitHub, Slack, or Discord.",
"Requires user-provided sprint data, team updates, and metrics.",
"Does not calculate velocity or burndown from live project systems.",
"Templates may need adjustment for non-Scrum or highly regulated workflows."
],
"use_cases": [
{
"title": "Prepare Daily Standups",
"description": "Turn team updates into a concise standup agenda with blockers, planned work, and action items.",
"target_user": "Scrum master"
},
{
"title": "Run Sprint Retrospectives",
"description": "Organize wins, problems, learnings, team health, and accountable improvements after each sprint.",
"target_user": "Engineering manager"
},
{
"title": "Report Sprint Progress",
"description": "Summarize sprint status, risks, decisions, metrics, and next priorities for stakeholders.",
"target_user": "Product manager"
}
],
"prompt_templates": [
{
"title": "Create A Basic Standup",
"scenario": "Beginner daily ceremony setup",
"prompt": "Create a daily standup for [team name]. Include yesterday, today, blockers, and action items. Keep it concise and easy to share."
},
{
"title": "Summarize Async Updates",
"scenario": "Team members posted updates in chat",
"prompt": "Summarize these async standup updates: [paste updates]. Group work completed, planned work, blockers, owners, and required follow-up."
},
{
"title": "Facilitate A Retrospective",
"scenario": "End of sprint team discussion",
"prompt": "Prepare a sprint retrospective for sprint [number]. Use these metrics and notes: [details]. Include wins, issues, learnings, health signals, and action items."
},
{
"title": "Build A Sprint Health Review",
"scenario": "Advanced sprint status and risk review",
"prompt": "Create a sprint health review from this sprint data: [details]. Include progress, burndown summary, risks, decisions needed, team health, and next focus areas."
}
],
"output_examples": [
{
"input": "Daily standup for five engineers with two blockers and three priorities.",
"output": "A concise standup agenda with individual updates, a blocker summary, named owners, and same-day follow-up actions."
},
{
"input": "Sprint retrospective notes with velocity, team mood, wins, and problems.",
"output": "A retrospective summary covering what went well, what did not, root causes, learnings, team health, and accountable improvements."
},
{
"input": "Weekly sprint status for stakeholders.",
"output": "A progress report with shipped work, active work, metrics, risks, decisions needed, and next week priorities."
}
],
"best_practices": [
"Provide current sprint goals, team names, known blockers, and relevant metrics.",
"Ask for owners and due dates when action items are created.",
"Review prior retrospective actions before generating a new retrospective."
],
"anti_patterns": [
"Do not use vague blockers without the support needed to unblock work.",
"Do not ask the skill to replace facilitator judgment or team discussion.",
"Do not omit sprint context when requesting progress summaries or retrospectives."
],
"faq": [
{
"question": "What ceremonies does this skill support?",
"answer": "It supports daily standups, async standups, sprint retrospectives, sprint progress reviews, team health checks, and weekly summaries."
},
{
"question": "Can it help with asynchronous standups?",
"answer": "Yes. It can format chat-based updates into completed work, planned work, blockers, and follow-up actions."
},
{
"question": "Does it integrate with Jira, GitHub, Slack, or Discord?",
"answer": "No. It uses information you provide and does not connect to external project or chat systems."
},
{
"question": "Can it create retrospective action items?",
"answer": "Yes. It can turn retrospective notes into clear action items with owners, due dates, and follow-up status."
},
{
"question": "Does it calculate agile metrics automatically?",
"answer": "No. It can organize metrics you provide, but it does not calculate live velocity, burndown, or cycle time."
},
{
"question": "Is it useful with Claude, Codex, and Claude Code?",
"answer": "Yes. The templates are text-based and work across Claude, Codex, and Claude Code workflows."
}
]
},
"file_structure": [
{
"name": "references",
"type": "dir",
"path": "references",
"children": [
{
"name": "daily-standup.template.md",
"type": "file",
"path": "references/daily-standup.template.md",
"lines": 180
},
{
"name": "RETROSPECTIVE.template.md",
"type": "file",
"path": "references/RETROSPECTIVE.template.md",
"lines": 155
}
]
},
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 59
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |