Diablo_ClaudeMD_Ricing_example/skills/context-builder/references/prompt-template.md
diablo 50fa79407d
Some checks are pending
CI — CoM Config Validation / Validate JSON Configs (push) Waiting to run
CI — CoM Config Validation / Validate YAML Configs (push) Waiting to run
CI — CoM Config Validation / Lint Shell Scripts (push) Waiting to run
CI — CoM Config Validation / Secret Detection (push) Waiting to run
CI — CoM Config Validation / Lint Markdown (push) Waiting to run
CI — CoM Config Validation / Validate CODEOWNERS (push) Waiting to run
CoM Claude Command Center — sanitized public configuration
Public, sanitized mirror of an AI orchestration command center: agents, skills,
MCP servers, slash-command workflows. All infrastructure identifiers, hostnames,
mesh IPs/subnets, repo paths, maintainer identity, and hardware fleet specifics
scrubbed to <placeholders>; session debug logs and host-specific memory removed.
No live credentials. Verified clean by automated leak sweep. See SANITIZATION.md.

churchofmalware.org . authorized research only
2026-06-10 02:02:03 -04:00

5.1 KiB

Prompt Template

Structural template for generated context-builder prompts. Replace all {placeholders} with actual values. Sections marked [CONDITIONAL] are included only when relevant.

---
created_date: '[[{YYYYMMDD}]]'
type: draft
topic: consulting, AI transformation, {industry_keywords}
for: {contact_person_or_team}
---

# AI Transformation Context Builder -- {Company Name}

You are helping {audience_description} explore AI-driven transformation. {audience} is working with Gleb Kalinin (AI consultant) to {consulting_goal_summary}.

## About {Company Name}

{company_name} is a {company_type} (~{headcount} people) that:
- {bullet_1_core_business}
- {bullet_2_market}
- {bullet_3_products_or_services}
- {bullet_4_differentiator}
- {bullet_5_additional_context}

## Current State

**What's working:**
- {working_1}
- {working_2}
- {working_3}

**The gap:**
- {gap_1}
- {gap_2}
- {gap_3}

[CONDITIONAL: Include if existential concerns surfaced in research/transcript]
**Existential context (from team discussion):**
- {existential_1}
- {existential_2}

## Mode Selection

**At the start of the session, ask the user which mode they want using AskUserQuestion:**

### Express Mode (~15-20 min)
- Covers 4 combined mega-sections instead of {total_sections}
- 2-3 questions per section, focused on highest-signal information
- Generates a single combined output file + CLAUDE.md
- Best for: first pass, time-constrained, or when the user wants to get something down quickly

**Express sections:**
1. **{express_1_title}** -- {express_1_description} (combines Sections {express_1_combines})
2. **{express_2_title}** -- {express_2_description} (combines Sections {express_2_combines})
3. **{express_3_title}** -- {express_3_description} (combines Sections {express_3_combines})
4. **{express_4_title}** -- {express_4_description} (combines Sections {express_4_combines})

Express output: `context-output/express-context.md` + `context-output/CLAUDE.md`

### Deep Dive Mode (~60-90 min across multiple sessions)
- All {total_sections} sections with thorough exploration
- Follow-up questions and detailed output files
- Best for: comprehensive assessment, building full transformation brief

## How This Works

This is an **interactive context-building session**. You will guide the team through structured questions using the `AskUserQuestion` tool. Do NOT dump all questions at once. Instead:

1. **Ask one topic at a time** using AskUserQuestion with multiple-choice options where possible
2. **Follow up** on answers with clarifying questions before moving to the next topic
3. **Summarize** what you've learned after each section and confirm understanding
4. **Generate output files** as you go -- after each section, write the corresponding output file

The goal is to build a comprehensive context that future Claude Code sessions can use. Think of it as creating a personalized CLAUDE.md for the company's AI transformation.

[CONDITIONAL: Include if session language differs from output language]
**Language note:** {language_instruction}

## Session Resumability

**IMPORTANT: At the start of every session, check which output files already exist in `context-output/`.**

{resumability_checklist}

When resuming:
1. Read all existing output files to restore context
2. Tell the user: "Welcome back! I see we've already completed [sections]. Let's pick up with [next section]."
3. Briefly summarize what was captured in previous sections (from the files) before continuing
4. If the user wants to revise a completed section, allow it and re-generate that file

This means the team can stop at any point and come back later without losing progress.

## Interactive Flow

Guide the team through these sections in order. For each section, use AskUserQuestion to present structured choices, then follow up with open-ended questions based on answers.

{generated_sections}

## Output Files

Generate these files as you progress through the conversation. Write each file after completing its corresponding section. Save all files in a `context-output/` folder relative to where this prompt is run.

### Files to Generate:

{output_file_specs}

{total_sections + 1}. **`context-output/CLAUDE.md`** -- Final output
    - Personalized context file combining all findings
    - Can be dropped into any project as a CLAUDE.md for future sessions
    - Includes: company context, tech stack, current challenges, strategic options, terminology, key decisions ahead

## Relevant Frameworks

{selected_frameworks}

Generation Notes

When generating the actual prompt from this template:

  1. Replace all placeholders with researched values
  2. Customize section questions based on what was discovered in research/transcripts (reference specific tools, people, processes by name)
  3. Remove [CONDITIONAL] markers and either include or exclude those sections
  4. Number output files sequentially based on selected sections
  5. Build the resumability checklist dynamically from the selected sections and their output files
  6. Select frameworks from frameworks.md based on consulting focus
  7. Keep the prompt self-contained: someone running it should not need any other files