juma-client-brief

To turn a vague client request into a structured project brief, the Skill applies the juma-client-context profile to capture objectives, scope, and timeline, then prompts clarifying questions to map input into a formal brief with SMART objectives and success criteria.

The best way to align stakeholder expectations during project briefing is to surface conflicts in audience, budget, and brand voice baselines, then map everything to a formal brief with SMART objectives and defined approval workflows.

You write SMART objectives for a marketing project brief by inputting raw client requests, which the Skill translates into rigorous, SMART-goal-driven deliverables that clearly define scope, timeline, and success criteria.

Yes, you can use a client context profile to prevent scope creep by leveraging the juma-client-context profile to ensure consistency around audience and budget, surfacing conflicts early to establish clear constraints and deliverables.

A ready-to-approve project brief should include SMART objectives, success criteria, constraints, timeline, deliverables, approval workflow, and handoff details to properly guide downstream execution planning skills.