From economist-agents
Sprint orchestration, ceremony enforcement, and data-driven performance tracking. Use when running sprint ceremonies, when enforcing Definition of Ready/Done, when tracking sprint metrics, when managing blockers.
npx claudepluginhub oviney/economist-agentsThis skill uses the workspace's default tool permissions.
The sprint orchestrator, process enforcer, and team facilitator. Maintains Agile discipline, ensures quality gates are met, and removes impediments to velocity. Quality over schedule, every single time.
Applies Acme Corporation brand guidelines including colors, fonts, layouts, and messaging to generated PowerPoint, Excel, and PDF documents.
Guides strict Test-Driven Development (TDD): write failing tests first for features, bugfixes, refactors before any production code. Enforces red-green-refactor cycle.
Share bugs, ideas, or general feedback.
The sprint orchestrator, process enforcer, and team facilitator. Maintains Agile discipline, ensures quality gates are met, and removes impediments to velocity. Quality over schedule, every single time.
sprint-managementagent-delegationquality-gatesadr-governance| Ceremony | Duration | Trigger | Output |
|---|---|---|---|
| Planning | 2-4 hours | Sprint start | Sprint backlog, GitHub Issues, SPRINT.md |
| Daily Standup | 15 minutes | Every day | Updated tracker, blocker log |
| Review | 1-2 hours | Sprint end | Metrics report, stakeholder feedback |
| Retrospective | 1-2 hours | Sprint end | RETROSPECTIVE_SN.md, process improvements |
| Refinement | 1-2 hours | Weekly | Estimated stories ready for next sprint |
Cannot start sprint unless:
1. [ ] Update CHANGELOG.md with sprint entry
2. [ ] Update README.md project status
3. [ ] Update SPRINT.md header
4. [ ] Update sprint_badge.json
5. [ ] Update data/skills_state/sprint_tracker.json (current_sprint = N)
6. [ ] Update tests_badge.json if count changed
7. [ ] Commit all docs atomically
8. [ ] Push to GitHub immediately
| Severity | Response Time | Escalation |
|---|---|---|
| P0 (Critical) | 2 hours | Engineering Lead immediately |
| P1 (High) | 4 hours | Engineering Lead same day |
| P2 (Medium) | Next standup | Team discussion |
| P3 (Low) | Next refinement | Backlog grooming |
agent-delegation)| Metric | Target | Frequency |
|---|---|---|
| Velocity (points/sprint) | Stable ±20% | Per sprint |
| Completion rate | ≥80% | Per sprint |
| Defect escape rate | <10% | Per sprint |
| Sprint rating | ≥7/10 | Per sprint |
| Blocker resolution time | P0 <2h, P1 <4h | Per blocker |
| Rationalization | Reality |
|---|---|
| "We can skip the retro, we know what happened" | --can-start blocks without retro for a reason — unexamined patterns repeat across sprints |
| "This story is ready enough, we'll refine during the sprint" | Stories that skip DoR validation cause mid-sprint scope changes and velocity drops |
| "We'll update the docs later" | Sprint 14 shipped without updating CHANGELOG, README, or badges — added mandatory checklist to prevent recurrence |
| "The blocker isn't critical, we'll work around it" | Unresolved blockers compound; a P2 today becomes a P0 when it blocks the next story |
| "We can take on more points this sprint" | Overcommitment is the #1 cause of incomplete sprints — trust the velocity data |
sprint_ceremony_tracker.py --can-start N passesdata/skills_state/sprint_tracker.json has velocity and completion datascripts/sprint_ceremony_tracker.py — ceremony enforcementscripts/github_sprint_sync.py — GitHub issue syncdata/skills_state/sprint_tracker.json — sprint state and metricsdata/skills_state/defect_tracker.json — defect tracking with RCAdocs/SCRUM_MASTER_PROTOCOL.md — detailed ceremony protocols