Constraint Identifier — Output Skill

What this produces: A single-file HTML document that serves as both an SOP and an executable workflow for constraint extraction. The CEO/owner uses it weekly to capture what's blocking progress, structured for their advisor to act on immediately.

Output filename: constraint-identifier-[client-firm].html

Required inputs: Client vision goals (2–3 measurable outcomes), client name and firm, advisor name, session day, delivery method (email, Slack, etc.).

Document Identity

The constraint identifier is the CEO's weekly brain dump tool. It anchors every conversation to their stated vision, then guides them through a structured extraction that separates symptoms from root causes. The output is a Constraint Brief — raw, diagnostic, unfiltered — that the advisor receives before the weekly session.

This is NOT an advisor tool. It's built for the CEO/owner to run independently, either with an AI agent (ChatGPT, Claude) or as a manual checklist. The advisor designs it, the client uses it.

How to Use This Skill

1. Get the client's 2–3 vision goals (measurable, specific)
2. Copy the HTML template below
3. Replace all {{PLACEHOLDER}} content with client-specific data
4. Customize the extraction prompts if the client's context requires it
5. Deliver to the client with instructions: "Run this every [day] before our session"

Core Methodology

The 5-Step Process

Why This Order Matters

Vision first, extraction second. If you skip the anchor, CEOs default to reporting what happened instead of diagnosing what's in the way. The vision reminder reframes the conversation from "status update" to "what's blocking progress toward where I said I want to go."

Constraint Brief Template

This is the output the CEO sends to the advisor. The structure is fixed — every brief uses these sections in this order.

CONSTRAINT BRIEF — [Date]

🎯 VISION REMINDER
[Vision goal 1]
[Vision goal 2]
[Vision goal 3 if applicable]

⬇️ DOWNSTREAM (What's showing up)
[Symptoms, friction, what they experienced this week — in their words]

⬆️ UPSTREAM (Root cause)
[Why it's happening — people, process, or clarity]

🚧 VISION IMPACT
[Which goal this blocks and how]

🔄 OWNERSHIP GAPS
[What they're still doing that someone else should own]

❓ OPEN ITEMS
[Anything else weighing on them]

🔁 PATTERN FLAG
[Note if this issue has come up before or sounds recurring]

Extraction Rules

These rules govern how the agent processes the CEO's input:

1. Preserve the CEO's voice — raw, unpolished, real. Do not soften or corporate-speak their words.
2. Separate symptoms from root causes — downstream (what's showing up) vs upstream (why it's happening).
3. Connect every constraint to a vision goal — if a constraint doesn't threaten a stated goal, probe whether the goal set is incomplete.
4. Flag recurring patterns — if this came up before, say so. Pattern flags feed into the advisor's constraint priority matrix.
5. Diagnostic, not communication — this brief is written for the advisor, not for the team. Direct, honest, unfiltered.

Guided Extraction Prompts

These are the default prompts. Customize for client context if needed, but keep the four categories.

What's in the Way

• What's blocking progress toward these goals right now?
• Where did things slow down, get stuck, or require you to step in this week?
• What keeps coming back that shouldn't still be a problem?

Root Cause

• If you had to guess — what's actually causing this?
• Is this a people issue, a process issue, or a clarity issue?

Ownership

• What did you do this week that someone else should be doing?
• What are you holding onto that you need to let go of?

Open

• What else is weighing on you, even if you can't name it yet?

Validation Prompt

If the CEO doesn't address which goal is being blocked:

"Which of your goals does this affect most — [goal 1] or [goal 2]?"

Executable Workflow Template

This is the text block the CEO pastes into their AI agent. Replace all {{PLACEHOLDER}} values.

RUN THIS WORKFLOW STEP BY STEP STARTING RIGHT NOW

================================================================================
PROCESS 1: VISION PRIME
================================================================================

TASK:
When the CEO opens this chat, display the vision anchor first. This frames everything that follows.

DISPLAY:
"CONSTRAINT IDENTIFIER

Before you start, remember your goals:

🎯 {{VISION_GOAL_1}}
   ({{GOAL_1_CONTEXT}})

🎯 {{VISION_GOAL_2}}
   ({{GOAL_2_CONTEXT}})

Everything you're about to talk through connects to this.

When you're ready, hit the voice button and talk through what's getting in the way. I'll organize it into a brief you can send to {{ADVISOR_NAME}} before {{SESSION_DAY}}."

TRANSITION:
Wait for the CEO to provide voice input or paste a transcript. Then proceed to Process 2.

================================================================================
PROCESS 2: GUIDED EXTRACTION
================================================================================

TASK:
If the CEO needs prompting, display these questions. Otherwise, let them talk freely and use these to check for completeness.

PROMPTS:

WHAT'S IN THE WAY
• What's blocking progress toward these goals right now?
• Where did things slow down, get stuck, or require you to step in this week?
• What keeps coming back that shouldn't still be a problem?

ROOT CAUSE
• If you had to guess — what's actually causing this?
• Is this a people issue, a process issue, or a clarity issue?

OWNERSHIP
• What did you do this week that someone else should be doing?
• What are you holding onto that you need to let go of?

OPEN
• What else is weighing on you, even if you can't name it yet?

VALIDATION:
If the CEO doesn't address which goal is being blocked, prompt:
"Which goal does this affect most — {{VISION_GOAL_1_SHORT}}, or {{VISION_GOAL_2_SHORT}}?"

TRANSITION:
"Got it. Let me pull this into a brief for {{ADVISOR_NAME}}."

================================================================================
PROCESS 3: EXTRACT & STRUCTURE
================================================================================

TASK:
Transform the brain dump into a structured Constraint Brief using the template below.

EXTRACTION RULES:
- Preserve the CEO's voice — raw, unpolished, real
- Do not soften or corporate-speak his words
- Separate symptoms from root causes
- Connect every constraint to which vision goal it threatens
- Flag anything that sounds like a recurring pattern

TONE GUIDANCE:
- This is diagnostic, not communication
- Direct, honest, unfiltered
- Written for the advisor, not the team

OUTPUT FORMAT:
CONSTRAINT BRIEF — [Date]

🎯 VISION REMINDER
{{VISION_GOAL_1}}
{{VISION_GOAL_2}}

⬇️ DOWNSTREAM (What's showing up)
[Symptoms, friction, what they experienced this week — in their words]

⬆️ UPSTREAM (Root cause)
[Why it's happening — people, process, or clarity]

🚧 VISION IMPACT
[Which goal this blocks and how]

🔄 OWNERSHIP GAPS
[What they're still doing that someone else should own]

❓ OPEN ITEMS
[Anything else weighing on them]

🔁 PATTERN FLAG
[Note if this issue has come up before or sounds recurring]

TRANSITION:
"Here's your Constraint Brief. Review it — if it captures what's on your mind, copy and email it to {{ADVISOR_NAME}} before {{SESSION_DAY}} morning."

================================================================================
PROCESS 4: REVIEW & SEND
================================================================================

TASK:
Present the draft brief and wait for CEO approval or edits.

IF EDITS REQUESTED:
Make the specific changes requested and re-present the brief.

IF APPROVED:
"You're all set. Send this to {{ADVISOR_NAME}} and your {{SESSION_DAY}} session will hit the ground running. Enjoy your weekend."

================================================================================
END OF WORKFLOW
================================================================================

HTML Document Structure

Sections (in order)

1. Header — Process tag, document title, version badge
2. Description — What this process does, in one paragraph (Cormorant Garamond, larger text)
3. Meta grid — Frequency, duration, who runs it
4. Vision Anchor — The client's 2–3 goals, displayed prominently
5. Context Required — Checklist of inputs the CEO should have in mind (recent friction, team feedback, open items from last session, etc.)
6. Process Flow — Mermaid diagram showing the 5 steps
7. Step Cards — Expandable cards for each step with description and outputs
8. Executable Workflow — Copyable text block for AI agent
9. Expected Outputs — What the process produces (Constraint Brief)
10. Footer — Draft/version status

Design Notes

• Light theme (client-facing document)
• Brand the document to the client's firm, not to Advisory OS
• Mermaid.js loaded via CDN for the process flow diagram
• Step cards use click-to-expand interaction
• Workflow block has a copy button for easy paste into AI agent

Customization Points

When building for a new client, these are the only things that change:

What Feeds Into This / What This Feeds

Upstream: Client's vision goals (set during onboarding or GPS conversation)

Downstream: Constraint Brief → Constraint Priority Matrix → Master Plan → Deployment Cycle

The constraint identifier is Step 1 in the weekly advisory loop. Without it, the advisor is extracting constraints during session time instead of solving them.

Checklist Before Delivery

• [ ] Client's vision goals are specific and measurable (not vague aspirations)
• [ ] Goal context explains what success looks like in concrete terms
• [ ] Extraction prompts make sense for this client's industry and role
• [ ] Workflow text has all placeholders replaced
• [ ] Copy button works on the workflow block
• [ ] Mermaid diagram renders correctly
• [ ] Step cards expand/collapse properly
• [ ] Document branded to client's firm (not AOS)
• [ ] Footer shows version and draft/active status
• [ ] Delivered with instructions on when and how to use it

Skill file for Advisory OS Constraint Identifier · v1.0 · February 2026