Clarify business goals, actors, constraints, and success measures before design.
npx skills add https://github.com/2zcory/skills --skill product-ba
Please help me install this Agent Skill. Skill: product-ba Source: https://github.com/2zcory/skills/tree/main/product-ba Command: npx skills add https://github.com/2zcory/skills --skill product-ba
Use when a task is heading toward design or implementation but the business problem, scope, stakeholders, workflow, or requirements are still unclear. Clarify the business goal, actors, constraints, business rules, and success measures first, using focused BA questioning when needed, then produce the lightest fitting BA artifact. Do not use this as the primary surface for a full software-project documentation system across requirements, design, and delivery handoff; use software-docs-system for that.
Clarify the business goal, actors, constraints, and success measures, then produce the lightest fitting BA artifact and reference software-docs-system for full documentation when needed.
High-intent search queries and answers about installing and using this skill.
Clarify business requirements by identifying the core problem, actors, constraints, rules, and success measures using focused questioning. This process ensures scope and stakeholder workflow are defined before moving into the design or implementation phases of a project.
The best way to create a lightweight BRD or user-story pack is to clarify the business goal and constraints first, then produce the lightest fitting artifact that captures stakeholder needs and success measures without generating overly heavy documentation.
When project scope and stakeholders are unclear before delivery, apply business analysis questioning to identify goals, constraints, and business rules. This produces clarification notes that define boundaries and ensure all actor workflows are documented prior to design.
This business analysis approach does not handle full software-project documentation. It focuses on clarifying requirements and producing lightweight artifacts, directing users to a comprehensive software-docs-system for complete requirements, design, and delivery handoff documentation.
You need to produce clarification notes when a task is heading toward design or implementation but the business problem, workflow, or stakeholder constraints remain undefined. This ensures goals and success measures are established before committing development resources.
Yes, you can use this method to define success measures and business rules. It specifically targets scenarios where the business problem is unclear, applying focused analysis to identify constraints and produce a scoped artifact that guides implementation.
yuyuxinliConvert feature requests into prioritized epics and sequenced Now/Next/Later roadmaps.
PedroGiudiceGenerate HTML architecture diagrams with data flows and deployment layers.
erikliebenGenerate technical design documentation with C4 diagrams and standardized templates.
Nir-BhayGuide backlog refinement sessions using the DEEP framework and Planning Poker.
