pace-biz

Capture opportunities, create Epics, and decompose Business Requirements.

73|6|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/arch-team/devpace --skill pace-biz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pace-biz
Source: https://github.com/arch-team/devpace/tree/main/skills/pace-biz
Command: npx skills add https://github.com/arch-team/devpace --skill pace-biz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the initial stages of product development by providing a structured way to capture business opportunities, define Epics, and decompose them into actionable requirements, ensuring strategic alignment from the outset.

Core Features & Use Cases

  • Opportunity Capture: Log new business ideas and market insights.
  • Epic Definition: Transform opportunities into well-defined Epics with clear objectives and success metrics (MoS).
  • Requirement Decomposition: Break down Epics into granular Business Requirements (BRs).
  • Strategic Alignment: Visualize and verify that development efforts directly support business goals.
  • Use Case: A product manager can use /pace-biz discover to brainstorm a new feature idea, then /pace-biz epic to formalize it as an Epic, and finally /pace-biz decompose to break it down into user stories for the development team.

Quick Start

Use the pace-biz skill to discover new product opportunities by describing your initial idea.

Frequently Asked Questions about pace-biz

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

FAQPage Schema
How do I capture business opportunities and translate them into Epics?

You can capture business opportunities and translate them into Epics by logging market insights, defining clear objectives and success metrics (MoS), and decomposing them into actionable Business Requirements for strategic alignment.

What is the best way to decompose Epics into granular Business Requirements?

The best way to decompose Epics into granular Business Requirements is by using structured requirement decomposition to break down well-defined Epics into actionable user stories for the development team.

How does strategic alignment checking work for product development efforts?

Strategic alignment checking works by visualizing and verifying that development efforts directly support business goals, ensuring upstream value chain coherence from opportunity capture to Epic management.

Can I generate product requirements from imported documents?

Yes, you can generate product requirements from imported documents, as the system supports interactive discovery, document import, and code-based inference for requirement generation.

Does product discovery support interactive brainstorming for new feature ideas?

Product discovery supports interactive brainstorming for new feature ideas, allowing product managers to formalize initial concepts into well-defined Epics with clear objectives and success metrics.

Why do I need opportunity mapping before defining Epics?

You need opportunity mapping before defining Epics because it streamlines initial product development by providing a structured way to capture business opportunities and ensuring strategic alignment from the outset.