GOST Participant Enablement Kit — Start Here
What This Kit Does
This kit produces an AI-powered participant enablement prompt that walks GOST participants through building a completed 12-Week Tactics Planner using any LLM (Copilot, ChatGPT, Claude, Gemini, etc.).
The prompt is self-contained — participants paste it into their AI tool, answer questions, and receive a formatted planner they can submit. The AI enforces SMART criteria, pushes back on vague answers, and produces output matching the client's 12-Week Tactics Planner template.
Production path: Gather client GOST data → Customize prompt → Generate participant document (docx) → Generate consultant brief (docx) → QC → Deliver to consultant → Consultant distributes to participants.
When to Use This Kit
Use this kit when:
- A client is running a GOST process (or any Goal → Objective → Strategy → Tactic cascade)
- Participants have been trained but are struggling to produce their quarterly tactics plans
- The consultant needs a scalable way to get submissions without hand-holding each participant
- There is resistance to the planning form — participants see it as "more work"
Trigger signals:
- Missed or late tactic submissions
- Pushback on the form format ("it's too much")
- Consultant reports that participants understood it in training but freeze when they sit down to do it
- A client-side leader who won't drive accountability (the tool replaces the need for that leader to push)
What It Produces
Two documents per deployment:
| Document | Audience | Format | Purpose |
|---|---|---|---|
| Participant Prompt Document | GOST participants | .docx | Instructions + the copy/paste prompt |
| Consultant Brief | The consulting advisor | .docx | How to send it, what to expect back, how to review output |
Naming convention:
- Participant:
[client]-gost-enablement-participant-v[n]-[mon]-[yyyy].docx - Brief:
[client]-gost-enablement-brief-v[n]-[mon]-[yyyy].docx
What This Kit Does NOT Do
- Does not build the GOST framework itself — the client must already have a Goal, Objectives, and department Strategies defined
- Does not replace GOST training — participants still need to understand what GOST is before using this tool
- Does not replace the consultant's judgment — the consultant reviews all output before it goes to leadership
- Does not generate Strategy Cards — this kit operates at the Tactics layer only
- Does not produce the 1:1 Meeting Planner or BSO Tool — those are separate deliverables
The Gap Protocol
A gap is any required input that is not available in the source material. Gaps are flagged, never filled. The build stops until the advisor resolves the gap.
See 01-gost-enablement-context.md for the full required inputs list and gap escalation procedure.
File Inventory
| File | Purpose | When to Use |
|---|---|---|
00-gost-enablement-start-here.md | Orientation and routing | Read first — every time |
01-gost-enablement-context.md | Required inputs and gap protocol | Before building — confirm all inputs are available |
02-gost-enablement-terminology.md | Locked vocabulary for GOST enablement | Reference throughout — terminology wins over any other usage |
03-gost-enablement-golden-example.md | Original deployment as the benchmark | When building — use as the reference for prompt structure, participant doc format, and output quality |
04-gost-enablement-quality.md | QC checklists (pre-build + post-build) | Gate 1 before building, Gate 2 after building |
05-gost-enablement-build-skill.md | Step-by-step production workflow | During build — follow sequentially |
06-gost-enablement-consultant-methodology.md | How the consultant assesses readiness and positions this tool with the client | Before the kit is triggered — when the consultant identifies the need |
Relationship to Other Kits
| Kit | Relationship |
|---|---|
| GOST Workshop Materials (training decks, facilitator guide) | Upstream — participants must be trained before this kit is relevant |
| Strategy Card & Instructions | Upstream — department strategies must exist before tactics can be planned |
| 12-Week Tactics Planner (template) | The output format — this kit's prompt produces content that matches this template |
| Weekly Meeting Planner (1:1 template) | Downstream — the planner's Weekly Progress Tracker feeds into 1:1 meetings |
| Constraint Priority Matrix | Parallel — participant resistance and adoption gaps surface as constraint evidence |
| Client Email Kit | May be used to draft the distribution email to participants |
Gold Standard Reference
The original deployment (March 2026) is the golden example for this kit. It was built for a mid-market B2B services company when participants resisted submitting Q2 tactics after completing GOST training. The prompt was tested against three simulated department leaders (Sales, IT, Client Services) with different personality types and produced complete, SMART-compliant planners in all three cases.
See 03-gost-enablement-golden-example.md for the full benchmark reference.