Overview

This skill guides a business analyst (Mary) through collaborative discovery to create a concise product brief. It follows a CORE workflow and relies on reading instructions from ./instructions.md and validating the final brief against ./checklist.md to ensure alignment.

How This Skill Works

The agent (Mary) uses the CORE module to drive a guided discovery session, gathers inputs from stakeholders, and defines scope, objectives, and success criteria. It then drafts the product brief and validates it against the provided checklist to ensure completeness before sign-off, following the Execution and Validation steps in the SKILL.md.

When to Use It

• When the user says 'let's create a product brief' or 'help me create a project brief' to initiate collaborative discovery.
• When starting a new product or project initiative that requires a clear, shared brief.
• When aligning multiple stakeholders on scope, goals, and success metrics.
• When you need a concise, actionable brief for development teams and stakeholders.
• When finalizing the brief and verifying it against a predefined checklist before sign-off.

Quick Start

1. Step 1: Say the trigger phrase, e.g., 'let's create a product brief' or 'help me create a project brief'.
2. Step 2: Mary reads and follows ./instructions.md to guide the discovery and input collection.
3. Step 3: Draft the product brief and verify it against ./checklist.md before finalizing.

Best Practices

• Kick off with clear objectives and target users to set the brief's direction.
• Capture constraints, assumptions, and success criteria early in the discovery.
• Facilitate collaborative sessions with key stakeholders to gather input.
• Execute strictly per the instructions in ./instructions.md and validate with ./checklist.md.
• Keep the brief concise, actionable, and aligned with business goals and metrics.

Example Use Cases

• Example 1: A startup uses the skill to draft a product brief for a new mobile app, aligning the team on goals and success criteria.
• Example 2: A product team creates a brief for a Q2 feature release to define scope and stakeholder responsibilities.
• Example 3: An internal tool project uses collaborative discovery to resolve conflicting requirements and publish a clear brief.
• Example 4: Stakeholders with divergent views participate in a discovery session to converge on a single brief.
• Example 5: After market research, the brief incorporates competitive insights and measurable KPIs for evaluation.

Frequently Asked Questions