Update strategic_review.yml -- add mission charter awareness and company proposal gate (Sprint 82)
This commit is contained in:
@@ -1,11 +1,12 @@
|
|||||||
name: strategic_review
|
name: strategic_review
|
||||||
description: "Crimson Leaf 24-hour strategic review -- full portfolio evaluation from each executive's perspective."
|
description: "Crimson Leaf 24-hour strategic review -- mission assessment, portfolio evaluation, gap identification, and escalation."
|
||||||
debug: true
|
debug: true
|
||||||
model: power
|
model: power
|
||||||
system: agent_prompt
|
system: agent_prompt
|
||||||
|
|
||||||
agent_prompt:
|
agent_prompt:
|
||||||
- "= identity.md"
|
- "= identity.md"
|
||||||
|
- "= mission.md"
|
||||||
|
|
||||||
participant_prompt:
|
participant_prompt:
|
||||||
- "= identity.md"
|
- "= identity.md"
|
||||||
@@ -39,12 +40,14 @@ steps:
|
|||||||
You are {agent.name}, participating in the Crimson Leaf Holdings strategic review.
|
You are {agent.name}, participating in the Crimson Leaf Holdings strategic review.
|
||||||
This is round {task.iteration} of the board session.
|
This is round {task.iteration} of the board session.
|
||||||
|
|
||||||
The portfolio report is above. Analyze it from YOUR perspective:
|
The portfolio report is above. Your mission charter is in your system prompt.
|
||||||
|
Analyze from YOUR perspective:
|
||||||
|
|
||||||
- If you are Edgar (The Operator): Focus on systems health, metrics, what's broken,
|
- If you are Edgar (The Operator): Focus on systems health, metrics, gaps in capability.
|
||||||
what needs fixing. Are companies executing? Are processes working?
|
Are companies executing? Are we moving toward the mission success criteria?
|
||||||
|
What gaps are blocking revenue? What should we PROPOSE to David?
|
||||||
|
|
||||||
- If you are Orion (The Visionary): Focus on opportunities, growth, what we're missing.
|
- If you are Orion (The Visionary): Focus on opportunities and what we are missing.
|
||||||
Are we building the right things? What should we start? What should we kill?
|
Are we building the right things? What should we start? What should we kill?
|
||||||
|
|
||||||
- If you are Sloane (The Dealmaker): Focus on marketing, visibility, revenue.
|
- If you are Sloane (The Dealmaker): Focus on marketing, visibility, revenue.
|
||||||
@@ -53,7 +56,7 @@ steps:
|
|||||||
Build on previous speakers' points. Disagree if you must -- this is a board debate.
|
Build on previous speakers' points. Disagree if you must -- this is a board debate.
|
||||||
|
|
||||||
When genuine consensus is reached across all perspectives, include exactly:
|
When genuine consensus is reached across all perspectives, include exactly:
|
||||||
"consensus_reached: true"
|
consensus_reached: true
|
||||||
If debate should continue, do NOT include that line.
|
If debate should continue, do NOT include that line.
|
||||||
|
|
||||||
- type: think
|
- type: think
|
||||||
@@ -64,24 +67,70 @@ steps:
|
|||||||
Synthesize the boardroom transcript into a STRATEGIC BRIEF for David.
|
Synthesize the boardroom transcript into a STRATEGIC BRIEF for David.
|
||||||
|
|
||||||
Structure:
|
Structure:
|
||||||
1. EXECUTIVE SUMMARY -- one paragraph on portfolio health
|
1. EXECUTIVE SUMMARY -- one paragraph on portfolio health and mission progress
|
||||||
2. CRITICAL ISSUES -- things that need immediate attention (if any)
|
2. MISSION GAP AUDIT -- assess each gap from the mission charter. Is Gap 1 (CLO)
|
||||||
3. OPPORTUNITIES -- ranked by priority
|
still the top priority? Has anything changed that elevates a different gap?
|
||||||
4. ACTION ITEMS -- specific tasks for David, formatted as:
|
3. CRITICAL ISSUES -- things needing immediate attention
|
||||||
|
4. OPPORTUNITIES -- ranked by priority
|
||||||
|
5. ACTION ITEMS -- specific tasks for David:
|
||||||
"David, [verb]: [details]"
|
"David, [verb]: [details]"
|
||||||
5. NEXT REVIEW -- what should we focus on in the next 24-hour review?
|
6. NEXT REVIEW -- focus for the next 24-hour review
|
||||||
|
|
||||||
Keep it actionable. David is one person -- prioritize ruthlessly.
|
Keep it actionable. David is one person -- prioritize ruthlessly.
|
||||||
|
|
||||||
MARKETING DISPATCH ASSESSMENT:
|
PROPOSAL GATE ASSESSMENT:
|
||||||
Check the portfolio data for Crimson Leaf Publishing projects.
|
Based on the gap audit, should Edgar submit a company proposal this cycle?
|
||||||
A book is "complete" if its project has a deliverable named MANUSCRIPT-README or
|
Criteria: gap is materially blocking revenue AND cannot be solved by existing resources
|
||||||
if the portfolio report shows a project_index task completed.
|
AND no proposal has been submitted in the last 30 days.
|
||||||
A book "needs marketing" if crimson_leaf_marketing shows no active campaign for it.
|
State one of: PROPOSAL_NEEDED: [company-slug] or PROPOSAL_NEEDED: none
|
||||||
|
|
||||||
|
MARKETING DISPATCH ASSESSMENT:
|
||||||
|
A book "needs marketing" if crimson_leaf_marketing shows no active campaign for it.
|
||||||
At the end of your brief, include:
|
At the end of your brief, include:
|
||||||
CLM_DISPATCH: <book-project-slug if a completed book needs CLM campaign, or "none">
|
CLM_DISPATCH: <book-project-slug if a completed book needs CLM campaign, or "none">
|
||||||
|
|
||||||
|
- type: think
|
||||||
|
max_tokens: 100
|
||||||
|
output_key: proposal_project_slug
|
||||||
|
hint: |
|
||||||
|
Read the PROPOSAL_NEEDED line from the strategic brief above.
|
||||||
|
If the value is "none", output exactly: none
|
||||||
|
Otherwise output exactly: incubation
|
||||||
|
|
||||||
|
Output ONLY one word. No explanation. No punctuation.
|
||||||
|
|
||||||
|
- type: think
|
||||||
|
max_tokens: 800
|
||||||
|
output_key: proposal_brief
|
||||||
|
hint: |
|
||||||
|
The proposal decision is: {proposal_project_slug}
|
||||||
|
|
||||||
|
If {proposal_project_slug} is "none", output exactly: none
|
||||||
|
|
||||||
|
Otherwise, write the task message for the company_proposal pipeline.
|
||||||
|
This brief becomes the input that drives the full business plan.
|
||||||
|
|
||||||
|
Include:
|
||||||
|
- Which company to propose (name, slug, purpose in one sentence)
|
||||||
|
- What gap it fills (specific -- what Edgar cannot do today without it)
|
||||||
|
- Why now (cost of waiting another 30 days)
|
||||||
|
- Proposed 90-day success criteria (measurable)
|
||||||
|
- Known constraints or dependencies
|
||||||
|
|
||||||
|
Be specific. This brief drives the entire proposal document.
|
||||||
|
|
||||||
|
Output ONLY the brief text. No labels. No preamble.
|
||||||
|
|
||||||
|
- type: tool
|
||||||
|
action: enqueue_strategy
|
||||||
|
optional: true
|
||||||
|
params:
|
||||||
|
company_slug: "crimson_leaf"
|
||||||
|
project_slug: "{proposal_project_slug}"
|
||||||
|
task_type: "company_proposal"
|
||||||
|
content: "{proposal_brief}"
|
||||||
|
agent_name: "edgar"
|
||||||
|
|
||||||
- type: think
|
- type: think
|
||||||
max_tokens: 100
|
max_tokens: 100
|
||||||
output_key: clm_dispatch_slug
|
output_key: clm_dispatch_slug
|
||||||
@@ -95,12 +144,12 @@ steps:
|
|||||||
max_tokens: 600
|
max_tokens: 600
|
||||||
output_key: clm_dispatch_message
|
output_key: clm_dispatch_message
|
||||||
hint: |
|
hint: |
|
||||||
If clm_dispatch_slug is "none", output exactly: none
|
If {clm_dispatch_slug} is "none", output exactly: none
|
||||||
|
|
||||||
Otherwise write a marketing campaign request for that book. Include:
|
Otherwise write a marketing campaign request for that book. Include:
|
||||||
- Book title, genre, audience, author
|
- Book title, genre, audience
|
||||||
- The manuscript is complete in Crimson Leaf Publishing Gitea repo
|
- The manuscript is complete in Crimson Leaf Publishing Gitea repo
|
||||||
- Request: full marketing campaign (strategy, social media, email, press release, ad copy)
|
- Request: full marketing campaign (strategy, social, email, press release, ad copy)
|
||||||
- Urgency: book has no active campaign and needs revenue generation
|
- Urgency: book has no active campaign and needs revenue generation
|
||||||
|
|
||||||
Book reference:
|
Book reference:
|
||||||
|
|||||||
Reference in New Issue
Block a user