📦
testing
85Build Reliable Test Automation
Weak tests slow releases and hide regressions. This skill guides test strategy, TDD, automation, coverage review, and Playwright web checks.
Coding & Development View
Skills agile-ceremonies
📦
agile-ceremonies
v1.0.1 Content revision r1 Safe ⚙️ External commands
Run Agile Ceremonies
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.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "agile-ceremonies" from https://skillstore.io/skills/89jobrien-agile-ceremonies.md and its manifest at https://skillstore.io/api/skills/89jobrien-agile-ceremonies/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "agile-ceremonies". Daily standup for five engineers with two blockers and three priorities.
Expected outcome:
A concise standup agenda with individual updates, a blocker summary, named owners, and same-day follow-up actions.
Using "agile-ceremonies". Sprint retrospective notes with velocity, team mood, wins, and problems.
Expected outcome:
A retrospective summary covering what went well, what did not, root causes, learnings, team health, and accountable improvements.
Using "agile-ceremonies". Weekly sprint status for stakeholders.
Expected outcome:
A progress report with shipped work, active work, metrics, risks, decisions needed, and next week priorities.
Security Audit
Safev6 • 7/5/2026 Open versioned report
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.
3
Files scanned
394
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (2)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/89jobrien-agile-ceremonies/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/89jobrien-agile-ceremonies?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/89jobrien-agile-ceremonies?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/89jobrien-agile-ceremonies/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/89jobrien-agile-ceremonies.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Joseph OBrien. (2026). agile-ceremonies security audit report (audit version 6) [Author version 1.0.1]. Skillstore. https://skillstore.io/skills/89jobrien-agile-ceremonies/audits/6BibTeX citation
@techreport{joseph-obrien-89jobrien-agile-ceremonies-2026,
author = {Joseph OBrien},
title = {agile-ceremonies security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/89jobrien-agile-ceremonies/audits/6},
note = {Author version 1.0.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "agile-ceremonies security audit report (audit version 6)"
version: "1.0.1"
type: report
authors:
- name: "Joseph OBrien"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/89jobrien-agile-ceremonies/audits/6"
identifiers:
- type: other
value: "skillstore:89jobrien-agile-ceremonies:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 41
Architecture
100
Maintainability
87
Content
70
Community
91
Spec Compliance
What You Can Build
Prepare Daily Standups
Turn team updates into a concise standup agenda with blockers, planned work, and action items.
Run Sprint Retrospectives
Organize wins, problems, learnings, team health, and accountable improvements after each sprint.
Report Sprint Progress
Summarize sprint status, risks, decisions, metrics, and next priorities for stakeholders.
Try These Prompts
Create A Basic Standup
Create a daily standup for [team name]. Include yesterday, today, blockers, and action items. Keep it concise and easy to share.
Summarize Async Updates
Summarize these async standup updates: [paste updates]. Group work completed, planned work, blockers, owners, and required follow-up.
Facilitate A Retrospective
Prepare a sprint retrospective for sprint [number]. Use these metrics and notes: [details]. Include wins, issues, learnings, health signals, and action items.
Build A Sprint Health Review
Create a sprint health review from this sprint data: [details]. Include progress, burndown summary, risks, decisions needed, team health, and next focus areas.
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.
Avoid
- 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.
Frequently Asked Questions
What ceremonies does this skill support?
It supports daily standups, async standups, sprint retrospectives, sprint progress reviews, team health checks, and weekly summaries.
Can it help with asynchronous standups?
Yes. It can format chat-based updates into completed work, planned work, blockers, and follow-up actions.
Does it integrate with Jira, GitHub, Slack, or Discord?
No. It uses information you provide and does not connect to external project or chat systems.
Can it create retrospective action items?
Yes. It can turn retrospective notes into clear action items with owners, due dates, and follow-up status.
Does it calculate agile metrics automatically?
No. It can organize metrics you provide, but it does not calculate live velocity, burndown, or cycle time.
Is it useful with Claude, Codex, and Claude Code?
Yes. The templates are text-based and work across Claude, Codex, and Claude Code workflows.
Developer Details
Author
Joseph OBrienLicense
MIT
Author version
v1.0.1
Skillstore revision
r1
Ref
c4037264bbd363c572662d6154a3ab28f5ca4f53
Maintenance freshness
7/18/2026
Usage
7 downloads · 184 views
File structure
More from Joseph OBrien
📦
debugging
84Debug Errors and Root Causes
Errors and incidents are hard to triage when evidence is spread across logs, stack traces, and services. This skill structures diagnosis, parses logs, identifies patterns, and guides minimal fixes.
Coding & Development View
📦
code-context-finder
83Find Code Context Faster
Developers often lose time tracing why code exists and what depends on it. This skill prompts Claude, Codex, or Claude Code to gather related graph knowledge, callers, imports, and tests before changes.
Coding & Development View
📦
skill-creator
83Create Effective AI Skills
Building reusable AI skills is hard when structure, resources, and validation rules are unclear. This skill provides a practical workflow for designing, writing, validating, and packaging skills.
Documentation View
📦
dependency-management
83Manage Dependency Updates and Audits
Dependency updates can hide vulnerabilities, license issues, and breaking changes. This skill guides audits, safe upgrades, and reports across common package managers.
DevOps & Infrastructure View
📦
prompt-optimization
82Optimize LLM Prompts and Agent Instructions
Weak prompts create inconsistent model outputs and slow AI feature development. This skill helps structure prompts, examples, constraints, and output formats for Claude, Codex, and Claude Code.
Productivity View
Related Skills
View all📦
sprint-planner
80Plan Agile Sprints With Clear Capacity
by shubhamsaboo
Sprint planning often stalls when scope, estimates, and capacity are unclear. This skill guides Claude, Codex, and Claude Code to create sprint goals, backlog tables, risks, and done criteria.
Productivity View
📦
task-planning
79Plan Agile Tasks and User Stories
by supercent-io
Teams often receive broad feature requests without clear tasks, priorities, or acceptance criteria. This skill turns feature ideas into user stories, sprint backlog items, dependencies, and Definition of Done checks.
Productivity View
📦
task-estimation
77Estimate Agile Tasks With Story Points
by supercent-io
Teams need consistent estimates for sprint planning and roadmaps. This skill guides story points, planning poker, sizing, risks, and task breakdowns.
Productivity View
📦
agile-product-owner
76Create Agile Stories and Sprint Plans
by alirezarezvani
Product teams often lose time turning ideas into clear, testable backlog items. This skill helps create user stories, acceptance criteria, estimates, and capacity-based sprint plans.
Productivity View
📦
agile-planning
74Plan Agile Releases with Sprint Roadmaps
by Emz1998
Release planning often breaks down when timelines, tasks, and dependencies are scattered. This skill turns project context into sprint schedules, task codes, milestones, and roadmap views.
Productivity View
📦
planning-sprints
71Plan Focused, Achievable Sprints
by C0ntr0lledCha0s
Teams often overcommit because backlog priority, capacity, and dependencies are considered separately. This skill combines them into a structured sprint plan with measurable goals.
Productivity View