Agentification Readiness Checklist

Story-Level Readiness (per story):
[ ] Acceptance criteria are specific, measurable, and complete
[ ] No requirement for judgment calls not captured in the criteria
[ ] Technical context (architecture decisions, patterns, constraints) documented
[ ] Security sensitivity assessed — conservative areas require human-primary development
[ ] Integration points with other in-progress work identified
[ ] Definition of Done criteria can be verified programmatically

Team-Level Readiness:
[ ] Team has agreement on which story types are agent-appropriate
[ ] Human review process for agent-produced PRs is defined and staffed
[ ] Agent failure protocol exists (what happens when an agent produces unacceptable output)
[ ] Organizational approval for agentic workflow in this codebase is confirmed
[ ] Monitoring for agent-produced code in production is in place

ScrumMaster Role:
[ ] Sprint planning accounts for human review time as explicit capacity
[ ] Retrospective agenda includes agent quality patterns
[ ] Stakeholder communication covers what agentic production means for quality assurance

// Story assessment before handing to agent:

story: "Add rate limiting to the public API"

readiness: {
  acceptanceCriteria: "PASS — specific limits, error codes, and headers documented",
  technicalContext: "PASS — existing middleware pattern documented in team wiki",
  securitySensitivity: "REVIEW — rate limiting touches authentication paths; human review required pre-merge",
  integrationRisk: "PASS — isolated middleware layer, no concurrent changes",
  verifiability: "PASS — behavior testable with automated rate limit hit scenarios"
}

decision: "Agent-appropriate with human security review before merge"

note: "The story directly above this in the backlog — 'Redesign API authentication' — is NOT agent-appropriate. Novel architecture decision. Human-primary."