product

Document requirements, user stories, and acceptance criteria for Azure services.

6|3|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/jongio/azd-copilot --skill product-jongio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product
Source: https://github.com/jongio/azd-copilot/tree/main/cli/src/internal/assets/skills/product
Command: npx skills add https://github.com/jongio/azd-copilot --skill product-jongio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of defining product requirements, user stories, and acceptance criteria, ensuring alignment with Azure capabilities and best practices.

Core Features & Use Cases

  • Requirements Gathering: Systematically document functional and non-functional requirements.
  • User Story Creation: Craft clear, actionable user stories with Azure context.
  • Acceptance Criteria Definition: Define testable criteria for feature validation.
  • Azure Feasibility: Validate requirements against Azure service limits and capabilities.
  • Use Case: When starting a new feature, use this Skill to document its requirements, create user stories for the development team, and define acceptance criteria to ensure it meets business needs and technical constraints on Azure.

Quick Start

Use the product skill to create a user story for a new authentication feature.

Frequently Asked Questions about product

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

FAQPage Schema
How do I create user stories that meet INVEST criteria for Azure projects?

To create user stories meeting INVEST criteria for Azure, systematically document functional and non-functional requirements, then map them to relevant Azure services to ensure technical feasibility and actionable implementation.

What is the process for defining acceptance criteria for Azure-based features?

Defining acceptance criteria for Azure-based features involves validating documented requirements against Azure service limits and capabilities, ensuring the criteria are testable and align with both business needs and technical constraints.

How do I document functional and non-functional requirements for an agile project?

Documenting functional and non-functional requirements for an agile project requires identifying stakeholders, capturing system behaviors, and validating constraints against Azure feasibility to ensure comprehensive requirement coverage.

Can I validate product requirements against Azure service limits and capabilities?

Yes, you can validate product requirements against Azure service limits and capabilities by performing Azure feasibility checks that map user stories and acceptance criteria to specific Azure services for implementation.

What's the best way to gather requirements from stakeholders for Azure development?

The best way to gather requirements from stakeholders for Azure development is to systematically identify stakeholders, document their needs as functional and non-functional requirements, and verify alignment with Azure capabilities.