Throughput by Type
Per Project, per week: count of Issues moved to Status: Done bucketed by IssueType (Story / Bug / Task / Improvement). Pairs with created-count to surface bug pile-up vs. story delivery rate.
Work to verified outcome
Apply the same workflow and quality checks to every delivery transition.
3 stages · 1 approval
Roles and responsibilities
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Work the board
Developers move their assigned Issues along the Workflow — ToDo → InProgress (stamps Issues.StartedAt, emails Assignee, places card in In Progress column on the Board), work the Issue (commit time via IssueWorkLog, post IssueComments, attach files via IssueAttachments, decrement Remaining), open a git PR that the auto-link-to-pr webhook captures into PullRequestLinks (PR opening records linkage only; Projects.AutoTransitionOnMerge applies only to a verified merge). Every status change runs through status-transition-routing, which validates the move against the matching WorkflowTransitions row, blocks if RequiredApproverRole is unmet, and runs the per-transition action. Every move into a column also runs wip-limit-enforcement, which blocks if the destination column's BoardColumns.WipLimit is exceeded. Every change appends an IssueHistory audit row.
Resolve blockers
The daily-standup-digest schedule fires weekday mornings at the Project's StandupTimezone, posts the per-squad digest (In-Progress moved-yesterday, Done moved-yesterday, Blocked, At-Risk by sprint days remaining vs. remaining estimate) to the Project's NotifyTo channel. Issues Status: Blocked carry an IssueLinks row of type IsBlockedBy pointing at the blocker; resolving the blocker (transitioning the blocking Issue to Done) runs the UnblockLinks on-transition action. Bugs created or updated trigger bug-priority-recompute to refresh PriorityScore from Severity + ReportedFrequency + ReachEstimate; threshold crossings flip Priority: Critical and notify the on-call Engineer + Project Lead.
Approval required
Verify result
When a git PR linked to an Issue is merged into the protected branch, the auto-link-to-pr webhook updates the PullRequestLinks row (Status: Open → Merged, MergedAt stamped); if Projects.AutoTransitionOnMerge is on, the Issue auto-transitions InReview → Done (subject to any QA gate in WorkflowTransitions). On InReview → Done, status-transition-routing flips Issues.ResolvedAt, Issues.Resolution: Fixed, recomputes current sprint progress without incrementing an unversioned historical counter, and unblocks any IssueLinks of type IsBlockedBy pointing at this Issue. QA verification of bug-type Issues holds at InReview until QA approves the gated transition.
Approvals and exception handling
1 approval required in this process
-
Verify result
QA / Tester signs · closes the process
TransitionApprovals, PullRequestLinks, Issues - A provider merge cannot bypass QA.
- An approval belongs to the current issue revision.
- Concurrent moves cannot exceed the final available WIP slot.
When the process needs attention
-
exception
Resolve blockers
The daily-standup-digest schedule fires weekday mornings at the Project's StandupTimezone, posts the per-squad digest (In-Progress moved-yesterday, Done moved-yesterday, Blocked, At-Risk by sprint days remaining vs. remaining estimate) to the Project's NotifyTo channel.
-
hold
Verify result
QA verification of bug-type Issues holds at InReview until QA approves the gated transition.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Work the board | IssuesWorkflowTransitionsBoardColumns | Validate transitions and atomic WIP limits |
| 2 Resolve blockers | IssueLinksIssues | Preserve other outstanding dependencies |
| 3 Verify result | TransitionApprovalsPullRequestLinksIssues | Record independent quality evidence |
Process reports
All reportsBacklog Health
Per Project: Backlog count by IssueType, by Priority, and by ParentEpic; share of Backlog rows missing required Estimates (per IssueTypes.RequiresEstimate); share missing FixVersion. The Product Owner's grooming worksheet.
Cycle Time and Lead Time
Per Project, per IssueType: distribution of elapsed time Created → ResolvedAt (lead time) and StartedAt → ResolvedAt (cycle time), with p50 / p90 markers. Diagnoses queue length and review-stage delays by status.
Bug SLA Attainment
Per Project, per Severity: Bugs filed in the trailing 30 days, count resolved within the per-Severity SLA target (Sev1: 24h, Sev2: 3 business days, Sev3: 10 business days, Sev4: best-effort), and on-time-rate percent. The QA + on-call leadership report.
Run by an agent
Agent support
PM for IT Projects owns the backlog, issue workflow, sprint records and reviewed release cut. Git and CI provide authenticated evidence; deployment, customer billing and employment records remain in their source systems. Proto can explain a gate but cannot manufacture QA approval or a successful deployment.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› work to verified outcome · work the board on Issues, WorkflowTransitions, BoardColumns
✓ Developers move their assigned Issues along the Workflow — ToDo → InProgress (stamps Issues.StartedAt, emails Assignee, places card in In Progress column on the Board), work the Issue (commit time via IssueWorkLog, post IssueComments, attach files via IssueAttachments, decrement Remaining), open a git PR that the auto-link-to-pr webhook captures into PullRequestLinks (PR opening records linkage only; Projects.AutoTransitionOnMerge applies only to a verified merge).
› work to verified outcome · resolve blockers on IssueLinks, Issues
✓ The daily-standup-digest schedule fires weekday mornings at the Project's StandupTimezone, posts the per-squad digest (In-Progress moved-yesterday, Done moved-yesterday, Blocked, At-Risk by sprint days remaining vs.
› work to verified outcome · verify result on TransitionApprovals, PullRequestLinks, Issues
⏸ approval · waiting for the qa / tester
Other processes
3 moreIntake to sprint commitment
Turn incoming work into a prioritised, reviewed iteration scope.
3 stages · 0 approvals
Completed work to release cut
Review eligible issue scope before recording the release version.
3 stages · 1 approval
Sprint close to next plan
Preserve closed outcomes before rolling work into the next iteration.
3 stages · 0 approvals