brief

To frame a product discovery brief, generate a structured template enforcing required sections like the problem, who is affected, and discovery questions. This ensures consistent initiative alignment and reduces wasted cycles across PM workflows.

The best way to structure an initiative proposal is using a validated brief template. It enforces required sections such as the bet and decision points, ensuring clear stakeholder alignment and consistent product management documentation.

Write a problem definition brief by applying a structured template to your discovery sprint. It enforces required sections including the problem and who is affected, validating metadata to ensure clear problem framing and alignment.

Yes, you can use persona references from product.local.md when generating a problem brief. The skill supports integrating these references to ensure the problem framing accurately reflects the affected user segments.

Required sections for a discovery brief include the problem, who is affected, discovery questions, and the bet. Enforcing these template sections ensures consistent outputs and validates metadata for effective stakeholder alignment.

Yes, this brief generation approach integrates with related PM workflows like write-spec, competitive-brief, synthesize-research, and PRD. This integration supports end-to-end documentation across discovery sprints and initiative proposals.