with one click
net-agile
// Implement agile development practices and ceremonies for .NET projects
// Implement agile development practices and ceremonies for .NET projects
Automate Work Item -> Branch -> PR -> Evidence Pack for AI Coding Factory
Implement Scrum framework and team structures for .NET enterprise projects
Implement CQRS pattern with MediatR for .NET applications
Create Docker configuration for ASP.NET Core applications
Create domain models following Domain-Driven Design principles
Create GitHub Actions CI/CD pipelines for .NET applications
| name | net-agile |
| description | Implement agile development practices and ceremonies for .NET projects |
| license | MIT |
| compatibility | opencode |
| metadata | {"audience":".net-developers","methodology":"agile","frameworks":"scrum, kanban"} |
I help you implement enterprise agile practices:
Use this skill when:
## [ID] - [Title]
**Priority**: Must Have / Should Have / Could Have / Won't Have
**Estimate**: Story Points
**Sprint**: [Sprint Number]
**Status**: Backlog / In Progress / In Review / Done
### User Story
As a [type of user],
I want to [perform an action],
So that I can [achieve a goal].
### Acceptance Criteria
- [ ] Given [precondition], when [action], then [expected outcome]
- [ ] [Additional criteria]
- [ ] [Edge cases]
### Definition of Done
- [ ] Code written and reviewed
- [ ] Unit tests with >80% coverage
- [ ] Integration tests pass
- [ ] Documentation updated
- [ ] Code quality checks pass
- [ ] Deployed to staging
### Tasks
- [ ] [Technical task 1]
- [ ] [Technical task 2]
- [ ] [Technical task 3]
### Definition of Ready
- [ ] User story has clear acceptance criteria
- [ ] Technical approach defined
- [ ] Dependencies identified
- [ ] Story estimated by team
- [ ] DoD agreed upon
### Notes
[Additional context, constraints, or risks]
## Sprint [Number] Planning
**Start Date**: [Date]
**End Date**: [Date]
**Sprint Goal**: [Brief goal statement]
### Team Velocity
- Previous Sprint Velocity: [points]
- Current Sprint Capacity: [points]
### Stories in Sprint
| ID | Story | Points | Priority | Owner |
|-----|-------|--------|----------|--------|
| 1 | | | | |
| 2 | | | | |
### Risks and Impediments
- [ ] [Risk 1]
- [ ] [Risk 2]
### Definition of Done for Sprint
- [ ] All user stories meet story DoD
- [ ] All tests pass (unit, integration, E2E)
- [ ] Code review completed
- [ ] Documentation updated
- [ ] Deployed to staging
- [ ] Stakeholder acceptance
- [ ] Sprint retrospective completed
## Daily Standup - [Date]
### Team
- [ ] Team Member 1
- [ ] Team Member 2
- [ ] Team Member 3
### Updates
**[Name]**:
- **Yesterday**: What did I complete?
- **Today**: What will I work on?
- **Blockers**: Any impediments?
**[Name]**:
- **Yesterday**: What did I complete?
- **Today**: What will I work on?
- **Blockers**: Any impediments?
### Action Items
- [ ] [Action item 1]
- [ ] [Action item 2]
## Sprint [Number] Retrospective
**Date**: [Date]
**Participants**: [List]
### What Went Well
1. [Positive outcome 1]
2. [Positive outcome 2]
3. [Positive outcome 3]
### What Didn't Go Well
1. [Challenge 1]
2. [Challenge 2]
3. [Challenge 3]
### Action Items for Next Sprint
| Issue | Action Item | Owner | Due Date |
|-------|-------------|--------|----------|
| 1 | | | |
| 2 | | | |
### Process Improvements
1. [Improvement 1]
2. [Improvement 2]
### Metrics
- Sprint Velocity: [points]
- Stories Completed: [count] / [total]
- Defects Found: [count]
- Deployments: [count]
- Average Cycle Time: [days]
User Story INVEST Criteria:
Story Estimation:
Sprint Length:
Capacity Planning:
Format:
Three Questions:
Purpose:
Agenda:
Format:
Key Questions:
Prioritization Frameworks:
MoSCoW Method:
Kano Model:
WSJF (Weighted Shortest Job First):
Backlog Grooming:
Enterprise DoD Checklist:
### Code Quality
- [ ] Code follows project coding standards
- [ ] Code reviewed and approved
- [ ] Static code analysis passes (SonarQube)
- [ ] No critical or high severity security vulnerabilities
- [ ] Code complexity within acceptable limits
### Testing
- [ ] Unit tests written and passing (>80% coverage)
- [ ] Integration tests written and passing
- [ ] E2E tests for critical user flows
- [ ] Performance tests meet SLA requirements
- [ ] Accessibility tests pass (WCAG 2.1 AA)
### Documentation
- [ ] API documentation updated (Swagger/OpenAPI)
- [ ] Code comments added for complex logic
- [ ] Architecture decision records (ADRs) updated
- [ ] User documentation updated (if applicable)
- [ ] Runbook updated (if applicable)
### Deployment
- [ ] Application builds successfully
- [ ] Deployed to staging environment
- [ ] Smoke tests pass on staging
- [ ] Database migrations tested
- [ ] Rollback plan documented
### Process
- [ ] User story meets acceptance criteria
- [ ] Stakeholder acceptance received
- [ ] QA sign-off completed
- [ ] Product owner approval received
Story DoR Checklist:
### Story Quality
- [ ] Story follows INVEST criteria
- [ ] Acceptance criteria are clear and testable
- [ ] Story is properly sized for single sprint
- [ ] Dependencies identified and documented
- [ ] Risks identified and mitigations planned
### Technical Readiness
- [ ] Technical approach understood
- [ ] Design documents reviewed
- [ ] API contracts defined
- [ ] Database schema changes identified
- [ ] Third-party integrations researched
### Team Readiness
- [ ] Story estimated by team
- [ ] Capacity verified
- [ ] Skills needed are available
- [ ] Owner assigned
- [ ] Dependencies scheduled
CI/CD Best Practices:
Key Agile Metrics:
Velocity Metrics:
Quality Metrics:
Process Metrics:
Delivery Metrics:
Use net-agile skill to:
1. Create user stories for a feature
2. Plan a new sprint
3. Set up Definition of Done
4. Create retrospective template
5. Track sprint velocity
6. Manage product backlog
I will generate complete agile artifacts and documentation.