skills.rest
TECH-HY
TECH-HYOFFICIAL
Explore all skills by this author →
GitHub

tpo-definition-of-ready

Validates backlog items against readiness checklists before assigning tasks to AI developer agents.

Updated Mar 22, 2026
Search Tags:#backlog refinement#acceptance criteria#agile#user stories#product owner#definition of ready#ai agent prompt
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-definition-of-ready-tech-hy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tpo-definition-of-ready
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/tpo-definition-of-ready
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-definition-of-ready-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague, incomplete, or risky tasks sent to AI developer agents produce poor implementations and rework. This Skill gives a Technical Product Owner a structured Definition of Ready gate so only clear, testable, and technically understood work items enter development. ## Core Features & Use Cases - Ready Checklist: A 16-point must-pass checklist covering goal clarity, scope, acceptance criteria, dependencies, and prompt specificity. - Readiness Dimensions: Separate product, technical, UX/UI, and acceptance readiness sections with question tables and required UI states. - Decision Framework: Ready / Ready with risk / Not ready / Blocked outcomes with a decision record template and red-flag list. - Use Case: Before handing a user story to an AI Developer Agent, run it through the checklist, fill the readiness question tables, and generate a structured prompt containing role, goal, scope, acceptance criteria, and required tests. ## Quick Start Use the definition-of-ready skill to evaluate this user story and tell me whether it is ready to send to the AI developer agent.

Frequently Asked Questions about tpo-definition-of-ready

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a user story is ready for development?▼

Run the story through the 16-point Ready checklist covering goal clarity, scope, acceptance criteria, priority, dependencies, and prompt specificity. All Must items must pass before the task is sent to an AI developer agent.

What is a Definition of Ready in agile backlog refinement?▼

A Definition of Ready is a gate confirming a backlog item is clear, small, testable, and technically understood enough for implementation to begin. It prevents vague or blocked work from entering development.

How do I write a prompt for an AI developer agent?▼

Include role, goal, scope, out of scope, technical context, acceptance criteria, required tests, and expected output format. The skill provides a ready prompt structure returning implementation summary, files changed, tests, and risks.

What makes acceptance criteria testable?▼

Testable criteria define positive cases, negative cases, edge cases, permission behavior, data validation, and UX states. Vague statements like "works correctly" or "improve UX" must be replaced with verifiable conditions.

When should a task be marked not ready?▼

Mark a task not ready when it combines unrelated goals, lacks acceptance criteria, has unclear user flows or technical boundaries, requires unmade architecture decisions, or depends on unavailable credentials, APIs, or designs.

Related Skills

Explore More Product & Management Skills→
CoreStack-EnggCoreStack-Engg

prd-writing

Converts stakeholder input into a complete PRD with problem statements, user stories, acceptance criteria, and RICE scoring.

Official
Advanced
ArthTech-AIArthTech-AI

subagent-driven-development

Dispatch fresh subagents for independent implementation tasks and review spec compliance before code quality.

Official
Advanced
foomakersfoomakers
6

verify-done

Validate work items against Definition of Done checklists.

Official
Advanced
scomofoscomofo

quick-design

Generate lightweight Quick Design Specs for small game changes.

Community
Intermediate