Agile product management, Scrum practices, and team collaboration for iterative product development.
npx skills add https://github.com/nicepkg/ai-workflow --skill agile
Apply agile methodologies to product development and team collaboration. Master sprint planning, backlog management, and continuous improvement.
| Day | Ceremony | Duration | Attendees |
|-----|----------|----------|-----------|
| Mon | Sprint Planning | 2h | Full team |
| Daily | Standup | 15min | Full team |
| Thu | Design Review | 1h | PM, Design, Eng |
| Fri | Sprint Review | 1h | Full team + stakeholders |
| Fri | Retrospective | 30min | Full team |
Sprint Goal: [One sentence describing sprint outcome]
Capacity:
- Team size: 5 engineers
- Working days: 10
- Available points: 40
Selected Stories:
1. [Story A] - 8 points - Owner: Dev1
2. [Story B] - 5 points - Owner: Dev2
3. [Story C] - 13 points - Owner: Dev3
...
Risks:
- [Risk 1]: Mitigation plan
- [Risk 2]: Mitigation plan
Definition of Done:
[ ] Code reviewed
[ ] Tests written
[ ] Documentation updated
[ ] PM accepted
As a [user type]
I want [action/capability]
So that [benefit/outcome]
Acceptance Criteria:
Given [context]
When [action]
Then [result]
Weekly Grooming (1 hour):
| Points | Complexity | Example |
|--------|------------|---------|
| 1 | Trivial | Config change |
| 2 | Small | Minor UI tweak |
| 3 | Medium | New simple feature |
| 5 | Large | Complex feature |
| 8 | XL | Multiple components |
| 13 | Epic | Should be broken down |
| Backlog | To Do | In Progress | Review | Done |
|---------|-------|-------------|--------|------|
| | | | | |
| WIP: - | WIP:3 | WIP: 3 | WIP: 2 | - |
| Hata | Olası Sebep | Çözüm |
|------|-------------|-------|
| Sprint overcommitment | Unrealistic capacity | Track velocity, be honest |
| Carryover stories | Scope creep | Stricter acceptance |
| Long standups | Too much detail | Time-box, parking lot |
| No retro action | No ownership | Assign owners, follow up |
[ ] Sprint goal clearly defined mi?
[ ] Stories properly sized mi?
[ ] WIP limits respected mi?
[ ] Retro actions implemented mi?
[ ] Velocity tracked mi?
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take nicepkg/agile from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.