Sales Workflow / Creative Briefs

What The Skill Has. What It Still Needs.

sales-creative-brief is a solid operating playbook for turning meeting or source material into an editable, client-ready simulator brief. It defines the thinking, quality bar, deliverable shape, and handoffs. It is not yet a single-command production pipeline.

7Defined workflow stages from intake through handoff

5Bundled example deliverables: four PDFs and one PPTX

2Detailed quality references: A+ standard and brief blending

1/1Scaffold test passing; no deliverable-quality test suite

Capability Split

Has vs. Does Not Have

The difference is important: the skill has strong procedural coverage, but most production steps are delegated to other tools or performed by the agent.

It Has

A Real Brief-Making Standard

Multiple intake modes: Fireflies URL or ID, raw transcript, and uploaded source brief or DOCX.
Client-voice extraction: concept summary, client-only remarks, goals, features, and intended experience.
Deadline-first and blended-source modes: fast editable drafts, source preservation, and structured merging.
Research direction: deep research, official product imagery, YouTube references, and capability evidence.
Visual direction: up to six concept images, source-grounded equipment, UI overlays, and client branding.
Editable deliverable spec: portrait 8.5 × 11 PPTX or DOCX working file, with PDF only when requested or final.
Greg A+ quality bar: exact equipment, flagship scenario, pilot boundaries, measurable value, visual proof, and a clear next decision.
ForgeFX handoffs: PowerPoint, concept-image refinement, Slack, SharePoint or ForgeMedia, Salesforce, and proposal channels.

It Does Not Have

An End-To-End Generator

No bundled Fireflies fetcher: the GraphQL query is documented, but the package has no transcript retrieval command.
No automated concept extractor: speaker filtering and client-voice synthesis are instructions, not implemented code.
No research collector: web, YouTube, and capability research depend on other skills and agent execution.
No image-production command: the visual brief is defined, but image generation and asset QA live elsewhere.
No deck builder: presentation production is delegated to the PowerPoint skill; this package supplies content requirements only.
No Kubota project material: no Kubota transcript, source brief, equipment facts, images, or working deck are bundled here.
No delivery automation: Slack, SharePoint, ForgeMedia, and Salesforce steps are procedural and externally gated.
No output-grade tests: current testing checks frontmatter and body presence, not factual grounding, visual quality, PPTX integrity, PDF rendering, or live-link access.

Execution Model

The Defined Workflow

The process is coherent and complete as a playbook. Automation depth varies by stage.

01 / Intake

Fetch & Parse

Fireflies transcript or source-document mode. Transcript API access is described, not implemented locally.

02 / Meaning

Extract Concept

Client-only remarks and a concise description in the client’s voice.

03 / Workspace

Scaffold Files

A working-folder command creates research, image, output, QA, and delivery placeholders.

04 / Evidence

Research

Deep research, product sources, relevant videos, and ForgeFX capability proof.

05 / Vision

Mockups

Three hero images plus three alternates, grounded in real client equipment and environments.

06 / Artifact

Build Brief

Portrait editable deck or document, structured around opportunity, experience, roadmap, and credibility.

07 / QA

Prove Quality

Greg A+ content bar, rendered-page checks, typography, widows, orphans, and source grounding.

08 / Handoff

Share Safely

Editable file first. PDF only by request. Verify accessible links before posting.

Automation Audit

Where The Package Stops

This is the clearest view of current production readiness.

Capability	Status	What Exists Now	What Is Missing
Skill routing and instructions	Present	Detailed SKILL.md with input modes, stages, content spec, guardrails, and handoffs.	Nothing material for routing.
Working-folder setup	Present	TypeScript command creates the expected folder tree and starter files.	It does not populate content or validate source completeness.
Transcript ingestion	Partial	Fireflies query and ID pattern are documented.	No executable fetch, retries, speaker-resolution checks, or source metadata audit.
Research and evidence	Partial	Research targets and evidence types are explicit.	No deterministic collector, source ledger, citation validator, or freshness check.
Concept images	Partial	Image count, source preference, visual intent, and branding rules are specified.	No prompts, generation command, contact sheet, or automated visual QA in this package.
Editable brief generation	Partial	Portrait format, page structure, copy bar, and document-polish rules are defined.	No local PPTX or DOCX renderer; production depends on the PowerPoint or Word workflow.
Quality assurance	Partial	A+ rubric and blending checklist cover content quality. One scaffold test passes.	No automated source-grounding, slide-layout, font, archive, PDF, or accessibility tests here.
Kubota readiness	Absent	The generic workflow can support Kubota once sources are supplied.	No current Kubota inputs, research packet, creative direction, image set, or editable brief.

Package Inventory

What Is Actually Bundled

Verified against the current skill directory and its passing scaffold check.

SKILL.md

The canonical workflow, content specification, guardrails, naming, and handoffs.

references/greg-a-plus-brief-standard.md

The operational quality bar for a client-ready, decision-driving brief.

references/blending-existing-creative-briefs.md

A focused method for combining drafts without producing a stitched-together document.

scripts/create-working-folder.ts

Creates the project workspace, starter markdown, image folder, outputs, and QA placeholders.

scripts/check-skill.ts

Checks that SKILL.md exists and has name, description, and body content.

examples/

Five deliverables across Vermeer, Skill Builders, and JetBlue for structural reference.

Preview drift found: the bundled SKILL.html is a useful styled rendering, but it does not fully reflect newer source-document mode, blended-source mode, the Greg A+ bar, and the current “PDF only on request” framing. This page audits the current markdown source rather than treating that HTML as canonical.

Bottom Line

Useful Today, But Agent-Driven

Good Use Today

Give an agent a transcript, source document, or Greg stub. The skill provides a disciplined path to an editable brief and prevents common failures: generic concepts, weak scope boundaries, decorative visuals, and premature PDFs.

Next Maturity Step

Turn the documented stages into a composable TypeScript pipeline: ingest, source ledger, concept packet, research bundle, visual prompts, editable artifact, deterministic QA, and verified delivery package.