pbi-create

Creates Scrum Product Backlog Items via interactive dialogue and Markdown output.

1|Updated Jun 10, 2016
One-click install
npx skills add https://github.com/yykamei/dotfiles --skill pbi-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pbi-create
Source: https://github.com/yykamei/dotfiles/tree/main/.config/opencode/skills/pbi-create
Command: npx skills add https://github.com/yykamei/dotfiles --skill pbi-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of Scrum Product Backlog Items (PBIs) by guiding users through a structured, interactive process to define requirements.

Core Features & Use Cases

  • Interactive PBI Generation: Define PBIs through a conversational interface.
  • Structured Output: Generates PBIs in a consistent Markdown format including Summary, Target User, Outcome, Acceptance Criteria, and Potential Issues.
  • Use Case: A product owner needs to quickly create a new PBI for a feature request. They can use this skill to articulate the 'what', 'why', and 'who' of the feature, ensuring all necessary components of a well-defined PBI are captured.

Quick Start

Use the pbi-create skill to generate a PBI for the request "Allow users to reset their passwords via email".

Frequently Asked Questions about pbi-create

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

FAQPage Schema
How do I create Scrum Product Backlog Items interactively?

To create Scrum Product Backlog Items interactively, engage in a guided dialogue that clarifies requirements, target users, desired outcomes, acceptance criteria, and potential risks, outputting a structured Markdown template.

What components are included in a well-defined Product Backlog Item?

A well-defined Product Backlog Item includes a summary, target users, desired outcomes, acceptance criteria, and potential issues, ensuring the what, why, and who of a feature request are fully captured.

How do I write user stories for agile requirements through dialogue?

Writing user stories for agile requirements through dialogue involves a conversational interface that prompts you to articulate feature details, ensuring all necessary components of a PBI are structured correctly.

Can I generate PBIs in Markdown format for my product backlog?

Yes, you can generate PBIs in Markdown format for your product backlog, as the interactive process ensures output strictly adheres to a specific Markdown template with Japanese polite speech for the summary.

Does interactive PBI generation work for defining acceptance criteria and risks?

Interactive PBI generation works for defining acceptance criteria and risks by facilitating a structured conversation that explicitly prompts you to identify potential issues and verify feature completion conditions.

What is the best way to define feature requests for a product owner?

The best way to define feature requests for a product owner is using an interactive PBI generator to streamline articulation of the what, why, and who through a structured conversational process.