tpo-development-stages-template

Defines eight product development stages with entry criteria, deliverables, and gate reviews.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-development-stages-template-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tpo-development-stages-template
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/tpo-development-stages-template
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-development-stages-template-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product development often lacks clear stage boundaries, causing teams to skip discovery, ship untested MVPs, or release without rollback plans. This Skill gives a Technical Product Owner a structured template that divides work from discovery to post-launch into eight gated stages, each with explicit entry criteria, deliverables, and exit criteria for controlling an AI Developer Agent. ## Core Features & Use Cases - Eight-Stage Lifecycle: Covers Discovery, Requirements, Architecture, UX/UI, MVP Build, QA and Stabilization, Release, and Post-Launch with defined objectives and activities. - Gate Checklists: Every stage includes checkbox-based entry and exit criteria plus a standardized Stage Gate Review decision format (Approved / Approved with Conditions / Rejected / Needs Rework). - Use Case: A Technical Product Owner managing an AI Developer Agent uses the template to verify that requirements are approved before architecture begins, that P0/P1 bugs are resolved before release, and that a rollback plan exists before production deployment. ## Quick Start Ask the agent to apply the development stages template to your product and produce a stage gate review for the current stage.

Frequently Asked Questions about tpo-development-stages-template

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

FAQPage Schema
How do I structure product development stages for a software project?

Divide work into eight stages: Discovery, Requirements, Architecture, UX/UI, MVP Build, QA and Stabilization, Release, and Post-Launch. Each stage needs a purpose, entry criteria, deliverables, and exit criteria so progress is verifiable before moving forward.

What is a stage gate review in product development?

A stage gate review is a decision checkpoint between development stages. It records a decision (Approved, Approved with Conditions, Rejected, or Needs Rework) along with evidence reviewed, open issues, risks, required fixes, and the owner and date.

How can a product owner control an AI developer agent?

Use stage-based checklists to gate the agent's work: require approved requirements before architecture, passing tests and code review before stabilization, and a rollback plan before release. The agent only advances when exit criteria are met.

What exit criteria should an MVP meet before release?

The MVP must have a working core user workflow, fixed critical bugs, passing tests, completed code and UX/UI review, and basic security checks. Before production release, P0 and P1 bugs must be resolved and a rollback plan must exist.

When should the discovery stage be skipped?

Discovery should not be skipped when the problem, target users, or business value are unclear. It can only conclude when the problem is stated, users are defined, assumptions and risks are documented, and a continue, pause, or stop decision is made.