Structured daily standup facilitation with three formats: 3-question updates, board-walking, and async remote standups.
Works with
Provides three standup formats (3 Questions, Walking the Board, and Slack-based async) adaptable to in-person, hybrid, and fully remote teams
Includes time-boxed 15-minute structure with built-in templates for tracking yesterday's work, today's plans, and blockers
Enforces core constraints: consistent daily timing, full team participation, and separation of problem-
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionstandup-meetingExecute the skills CLI command in your project's root directory to begin installation:
Fetches standup-meeting from supercent-io/skills-template and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate standup-meeting. Access via /standup-meeting in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
88
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
88
stars
## Daily Standup Template
**Date**: 2025-01-15
**Time**: 9:30 AM
**Duration**: 15 minutes
### Team Member A
- **Yesterday**:
- Completed user authentication API (#123)
- 2 code reviews
- **Today**:
- Implement JWT refresh token (#124)
- Write unit tests
- **Blockers**:
- Need Redis setup docs (ask Team Member B for help)
### Team Member B
- **Yesterday**:
- Frontend form validation (#125)
- **Today**:
- Implement profile page UI (#126)
- **Blockers**: None
### Team Member C
- **Yesterday**:
- Database migration (#127)
- Performance testing
- **Today**:
- Index optimization (#128)
- **Blockers**:
- Need production DB access (urgent)
### Action Items
1. [ ] Team Member B shares Redis docs with Team Member A (Today 10:00)
2. [ ] Team lead requests DB access for Team Member C (Today)
## Standup: Walking the Board
**Sprint Goal**: Complete user authentication system
### In Progress
- #123: User Login API (Team Member A, 80% done)
- #124: Refresh Token (Team Member A, planned)
- #125: Form Validation (Team Member B, 90% done)
### Blocked
- #127: DB Migration (Team Member C)
- **Blocker**: Access needed
- **Owner**: Team Lead
- **ETA**: This afternoon
### Ready for Review
- #122: Password Reset (Team Member D)
- Need reviewer
### Done
- #120: Email Service Integration
- #121: User Registration
### Sprint Progress
- **Completed**: 12 points
- **Remaining**: 13 points
- **On Track**: Yes ✅
Slack template:
[Daily Update - 2025-01-15]
**Yesterday**
- Completed user authentication flow
- Fixed bug in password validation
**Today**
- Implementing JWT refresh tokens
- Writing unit tests
**Blockers**
- None
**Sprint Progress**
- 8/13 story points completed
# Daily Standup - 2025-01-15
**Attendees**: 5/5
**Duration**: 12 minutes
**Sprint**: Sprint 10 (Day 3/10)
## Summary
- Stories Completed: 2 (5 points)
- Stories In Progress: 3 (8 points)
- Blockers: 1 (DB access permission)
## Individual Updates
[Refer to the 3 Questions format above]
## Action Items
1. Team lead: Request DB access (High priority)
2. Team Member B: Share Redis docs
3. Team Member D: Assign reviewer for PR #122
## Notes
- Sprint goal on track
- Team morale: High
#standup #daily-scrum #agile #team-sync #project-management
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
supercent-io/skills-template
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for standup-meeting matched our evaluation — installs cleanly and behaves as described in the markdown.
standup-meeting reduced setup friction for our internal harness; good balance of opinion and flexibility.
standup-meeting reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend standup-meeting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
standup-meeting reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in standup-meeting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend standup-meeting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend standup-meeting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in standup-meeting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for standup-meeting matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 69