GOST Participant Enablement — Build Skill

Step-by-step production workflow for building a GOST Participant Enablement deployment. Follow sequentially. Do not skip steps.

Step 1 — Read Reference Data

Always first.

Read the client's reference data file for canonical spelling of:

• Company name
• Department names
• Leader/manager names (if they appear in the prompt)
• Tool names (Salesforce, specific ATS, etc.)
• Any framework terminology the client uses differently (e.g., "pillars" instead of "objectives," "action items" instead of "tactics")

If the client uses different terminology for GOST components, document the mapping:

The prompt must use the client's terminology, not the kit's default.

Step 2 — Read the Source Material

Gather and read in this order:

1. Client's GOST documentation — training decks, strategy workshop outputs, Strategy Cards, Individual Tactics Template. This is the primary source for the company goal, objectives, and framework structure.
2. Client's 12-Week Tactics Planner template — the exact format participants are expected to produce. This determines the output format in the prompt.
3. Advisor notes or session transcripts — context on participant resistance, what's been tried, who the client-side leader is, what the friction points are.
4. Client's golden example (if available) — a real, completed tactic submission that the advisor has validated as high quality. This replaces or supplements the kit's default HR example.

Routing check: Is there enough GOST documentation to extract the goal and all objectives? If no — stop. This kit cannot be deployed without the client's actual GOST framework in place. Go back to the advisor.

Step 3 — Identify Gaps

Work through the Required Inputs tables in 01-gost-enablement-context.md. For each input, mark:

• Present — the input is available and confirmed
• Gap — the input is missing or ambiguous

Document all gaps in gap report format (see 01-gost-enablement-context.md).

Step 4 — Stop — Present Gap Report to Advisor

Do not build. Present the gap report. Wait for resolution.

For each gap, the advisor will either:

• Provide the missing input
• Make a decision (e.g., "use the kit's default HR example" or "the client calls objectives 'pillars' — use their language")
• Confirm that a recommended-but-not-required input can be skipped

Record all resolutions in the gap report resolution log. Proceed only after the advisor confirms all gaps are resolved.

Step 5 — Calculate Quarter Dates

Before building, calculate all date-dependent values for the target quarter:

1. Quarter label — e.g., "Q2 2026"
2. Quarter start date — e.g., April 1, 2026
3. Quarter end date — e.g., June 30, 2026
4. 12 weekly date ranges — Monday–Friday for each week, grouped by month:

• Month 1 (Weeks 1–4): Foundation & Quick Wins
• Month 2 (Weeks 5–9): Build & Iterate
• Month 3 (Weeks 10–12): Deliver & Measure

1. Month names — for the backward planning sections (e.g., June → May → April)
2. End state date — the last business day of the quarter

Write these values down. They will be inserted into the prompt and output template.

Step 6 — Open the Golden Example

Open 03-gost-enablement-golden-example.md and the original deployment participant document.

Extract the structural elements:

• Prompt opening instruction
• Company context block structure
• SMART framework section
• Golden example format
• 6-step instruction sequence
• Output format template structure

Refer to the "Values to Extract" table in 03-gost-enablement-golden-example.md to confirm which values must be replaced, which may be replaced, and which stay as-is.

Step 7 — Build the Enablement Prompt

Build the prompt by following this section order. Use the golden example as the structural reference. Replace all client-specific values.

Prompt Section Order

1. Opening instruction — "I need your help building a 12-Week Tactics Planner for my quarterly work plan. You're going to walk me through this step by step..."
2. Company context block:

• Framework name and definition (GOST or client's term)
• Goal (verbatim from client)
• All Objectives (verbatim from client, numbered)
• Strategy definition (annual, per department)
• Tactic definition (quarterly, per individual)

1. SMART criteria — definition of each element with bad/good example pair
2. Golden example — a fully worked tactic showing: department, leader, strategy, objective served, tactic statement, end state, KPIs (3), and backward plan (3 months)
3. Step 1 — About You — ask name, department, role, department strategy
4. Step 2 — Pick Your Tactic — help make it SMART, push back on vague/ambitious/disconnected
5. Step 3 — End State Vision — define success + 3 KPIs with targets
6. Step 4 — Backward Planning — walk backward: Month 3 → Month 2 → Month 1, with weekly actions, owners, hours, success criteria, dependencies
7. Step 5 — Reality Check — capacity analysis, resources, dependencies
8. Step 6 — Produce the Completed Planner — output format template with all sections, tables, and labeled placeholders

Output Format Template Build Order

Build the output template with these sections in order:

1. Header: Quarter label, Department, Leader, Strategy, Objective(s) Served
2. TACTIC (statement)
3. END STATE VISION: description + 3 KPIs with measure and target
4. BACKWARDS PLANNING CALENDAR:

• Month 3 (Weeks 10-12) — DELIVER & MEASURE: deliverables summary, weekly table, checkpoint
• Month 2 (Weeks 5-9) — BUILD & ITERATE: building blocks summary, weekly table, checkpoint
• Month 1 (Weeks 1-4) — FOUNDATION & QUICK WINS: setup summary, weekly table, checkpoint

1. CAPACITY ANALYSIS: hours allocated, available, buffer, weekly commitment
2. RESOURCE REQUIREMENTS: table (Skills, Tools, Budget, External)
3. DEPENDENCY TRACKER: table (Need, From Who, By When, Risk, Backup Plan)
4. WEEKLY PROGRESS TRACKER: 12-row table (Week, Plan, Actual, % Complete, Issues, Adjustments)
5. LESSONS LEARNED: What Worked, What Didn't, Adjustments for Next Quarter

Content Rules

• Write for the participant, not the advisor — plain language, no consulting jargon
• Use the client's terminology if it differs from GOST defaults
• All objectives must be verbatim — do not paraphrase or summarize
• The golden example must be a different department/role than the client's typical participant (avoids participants copying the example instead of doing their own thinking)
• Push-back instructions in Step 2 are non-negotiable — they are core to the prompt's effectiveness
• "Be friendly and conversational" closing is non-negotiable — tested and validated

Step 8 — Build the Participant Document

Build the .docx file with this section order:

1. Title — "GOST Tactics Planner — AI Enablement Tool" (or client's framework name)
2. What This Is — one paragraph
3. What You'll Get — one paragraph
4. Time — "About 15–20 minutes per tactic"
5. What You Need Before You Start — bullet list (department strategy, general idea of what to accomplish)
6. Have More Than One Tactic? — instruction to run once per tactic, new chat each time
7. Instructions — numbered steps (open AI tool, copy, paste, answer questions, repeat)
8. The Prompt — clearly bounded (START COPY / END COPY markers), visually distinct (shaded background or indented block)
9. End marker — "Do not copy anything below this line"

Step 9 — Build the Consultant Brief

Build the .docx file with this section order:

1. Title — "GOST Tactics Planner — AI Enablement Kit / Advisor Brief"
2. What This Does — one paragraph explaining the tool
3. How to Send It — suggested email template, ready to customize
4. What's Embedded in the Prompt — bullet list (goal, objectives, SMART, golden example, output format, push-back instructions)
5. Key Notes:

• One tactic per chat
• Works with any AI tool
• They can iterate
• Quarter dates are hardcoded (how to update for future quarters)
• No confidential data in the prompt
• This is a reusable kit

1. What You'll Get Back From Participants — description of the output format
2. Reviewing What Comes Back — checklist (Is it SMART? Does it roll up? Are KPIs real numbers? Is the plan realistic? Are dependencies identified?)

Step 10 — Run Gate 2 QC

Run the full Gate 2 checklist from 04-gost-enablement-quality.md.

1. Check for blocking failures first — fix any before scoring.
2. Score all sections.
3. If score < 90, identify failures and fix.
4. Re-run after fixes.
5. Document final score.

Step 11 — Deliver for Advisor Review

1. Save both documents to the correct client repo location (typically drafts/ or projects/[active]/builds/)
2. Present to the advisor with:

• Final QC score
• Any warnings or notes (e.g., "no client-specific golden example available — using kit default")
• Recommended next step (advisor reviews, then distributes to client)

1. Documents do not go to participants until the advisor approves.

When Building for a Future Quarter

When the same client needs the prompt updated for a new quarter:

1. Read the current quarter's deployment
2. Update all date-dependent values (Step 5)
3. Check if objectives or strategies have changed — update if so
4. Check if the client now has a real completed tactic that could replace or supplement the golden example
5. Run full Gate 2 QC
6. Deliver as a new version (increment version number in filename)