standup-meeting▌
supercent-io/skills-template · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Structured daily standup facilitation with three formats: 3-question updates, board-walking, and async remote standups.
- ›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-
Standup Meeting
When to use this skill
- Daily: same time, same place
- During a sprint: when team sync is needed
- Remote teams: async standup
Instructions
Step 1: 3 Questions Format
## 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)
Step 2: Walking the Board (Board-Based)
## 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 ✅
Step 3: Async Standup (Remote Teams)
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
Output format
Standup Minutes
# 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
Constraints
Required Rules (MUST)
- Time-boxed: within 15 minutes
- Same time: consistent time every day
- Everyone participates: every team member gives an update
Prohibited (MUST NOT)
- Problem Solving: Do not solve problems in the standup
- Status Report: Not a status report to management
- Late Start: Start on time
Best practices
- Stand Up: Actually stand up (keep it short)
- Parking Lot: Deep discussion goes to a separate time
- Visualize: Run it while looking at the board
References
Metadata
Version
- Current version: 1.0.0
- Last updated: 2025-01-01
- Supported platforms: Claude, ChatGPT, Gemini
Tags
#standup #daily-scrum #agile #team-sync #project-management
Examples
Example 1: Basic usage
Example 2: Advanced usage
How to use standup-meeting on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add standup-meeting
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches standup-meeting from GitHub repository supercent-io/skills-template and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate standup-meeting. Access the skill through slash commands (e.g., /standup-meeting) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★69 reviews- ★★★★★Noah Farah· Dec 20, 2024
Registry listing for standup-meeting matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Noah Haddad· Dec 20, 2024
standup-meeting reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Dev Anderson· Dec 16, 2024
standup-meeting reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Liam Wang· Dec 4, 2024
I recommend standup-meeting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Chen Jain· Nov 23, 2024
standup-meeting reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Li Perez· Nov 11, 2024
Useful defaults in standup-meeting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Chen Farah· Nov 11, 2024
I recommend standup-meeting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Layla Bhatia· Nov 7, 2024
I recommend standup-meeting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Mateo Rahman· Oct 26, 2024
Useful defaults in standup-meeting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Li Gonzalez· Oct 14, 2024
Registry listing for standup-meeting matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 69