pae/crimson_leaf
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sprint 53a: Skills Loop + Executive Templates

Browse Source 
- skills/skills.md: Root catalog/index of all skill guides
- skills/guides/PAETemplateGuide.md: How to write PAE-Lang YAML (distilled)
- skills/guides/PAEAgentGuide.md: agent.yml + identity.md schemas
- skills/guides/CorporateCharterGuide.md: Charter design reference
- templates/hire_agent.yml: CEO-authored agent provisioning with PAEAgentGuide injection
- templates/write_template.yml: CEO-authored template design with PAETemplateGuide injection
- templates/planning.yml: CL-specific boardroom→serialize→dispatch planning
- templates/boardroom.yml: CL-specific executive deliberation to consensus

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Baity
2026-03-10 09:06:20 -04:00
parent cdf596c67a
commit 6cf7440726
8 changed files with 1063 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

60
templates/boardroom.yml Normal file
View File

@@ -0,0 +1,60 @@
name: boardroom
description: "Crimson Leaf executive boardroom — rotating chair debate to consensus on strategic decisions."
debug: true
system: agent_prompt
participant_prompt:
- "= identity.md"
agent_prompt:
- "= identity.md"
sections:
- agent
- project
- history
- participants
- participants_prompt
- rag
- message
- instructions
steps:
- type: think
max_tokens: 16000
rotate_participants: true
loop:
max_iterations: 3
hint: |
You are {agent.name}. This is round {task.iteration} of the Crimson Leaf boardroom discussion.
This is an executive deliberation on a strategic decision. You are not lecturing.
You are writing YOUR perspective on what the group discussed this round.
Think of it as your meeting notes: what was said, who pushed back, what you argued,
what you think of the arguments you heard, where you agree or disagree.
CRIMSON LEAF CONTEXT:
Crimson Leaf is a holding company, incubator, and governance board. All deliberation
should be grounded in constitutional principles: charter alignment, portfolio coherence,
capital discipline, non-overlap, delegation safety, and architectural purity.
You have read the prior rounds above — react to them. Challenge what you disagree with.
Build on what resonates. Speak in your own voice. Make your case.
When the group has genuinely reached consensus across all perspectives, include exactly:
"consensus_reached: true"
If debate should continue, do NOT include that line.
- type: think
max_tokens: 8000
agent: first_available
hint: |
Synthesize the boardroom transcript into a clear recommendation.
Surface consensus, note unresolved tensions, and end with concrete next steps.
Ground all recommendations in Crimson Leaf's charter and constitutional principles.
- type: close
rag_update: false
adjudication:
enabled: false

95
templates/hire_agent.yml Normal file
View File

@@ -0,0 +1,95 @@
name: hire_agent
description: "CEO designs and provisions a new agent — skills-guided, adjudicated, directly committed."
debug: true
system: agent_prompt
agent_prompt:
- "= identity.md"
skills:
- guides/PAEAgentGuide.md
sections:
- agent
- project
- rag
- roster
- skills
- message
- rejection_feedback
- instructions
steps:
- type: think
hint: |
You are {agent.name}, executing the hiring process for Crimson Leaf LLC.
CONTEXT: Read the SKILLS & GUIDES section — it contains the PAE Agent Guide
which defines the exact file schemas you must produce.
DECISION PROCESS:
1. Review the TEAM ROSTER. Determine whether an existing agent already covers
the needed capability within their current directives.
2. If an existing agent can serve, explain why hiring is unnecessary.
Your package step should still output a hire_agent action, but with a
clear justification that may cause adjudication to reject if the hire is redundant.
3. If a new hire IS justified, design the complete agent:
AGENT DESIGN REQUIREMENTS:
- name: A distinctive, professional name fitting the role and company culture.
- role: One of: ceo, director, specialist, analyst, writer, editor, researcher.
- model: power for directors, default for specialists (unless deep reasoning needed).
- character.personality: One paragraph — temperament, working style, decision-making.
- character.stats: 1-10 scale — intelligence, creativity, diligence, adaptability, leadership.
- manages: Directors manage [specialists]. Specialists manage [].
- department: executive, operations, creative, research, engineering.
- supported_templates: ONLY templates that exist in the company templates/ directory.
- identity.md: Full narrative identity with Core Directives, Constitutional Principles,
Authority (authorized + not authorized), and Communication Style.
- system.md: Lean 3-8 line system prompt (You are..., MANDATE, SYSTEMIC RULES, OPERATING POSTURE).
CONSTRAINTS:
- Every hire must serve the company charter. Re-read the charter before finalizing.
- Crimson Leaf roster cap is 8 agents. Check roster size before proposing.
- No vanity roles, overlapping roles, or speculative roles.
- Each agent must have a distinct constitutional function.
- type: package
packet_type: IntakeResponse
hint: |
Convert the agent design into a strict JSON payload.
Output exactly ONE hire_agent action.
The agent_yml must be valid YAML. The identity_md and system_md must be complete markdown.
Do not include prose outside the JSON structure.
schema:
actions:
- type: hire_agent
agent_name: "string — the agent's display name"
role: "string — role slug: ceo, director, specialist, analyst, writer, editor, researcher"
agent_yml: "string — complete content of agent.yml (valid YAML)"
identity_md: "string — complete content of identity.md (full markdown)"
system_md: "string — complete content of system.md (lean markdown)"
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 85
deliverable_type: coordination
criteria:
charter_alignment:
weight: 25
description: "Agent serves the company charter and fills a genuine gap"
role_specificity:
weight: 20
description: "Agent has a distinct, non-overlapping function"
identity_quality:
weight: 20
description: "Identity is complete, constitutional, and actionable"
file_correctness:
weight: 20
description: "agent.yml, identity.md, and system.md are well-formed and consistent"
roster_discipline:
weight: 15
description: "Hire respects roster limits and avoids redundancy"

98
templates/planning.yml Normal file
View File

@@ -0,0 +1,98 @@
name: planning
description: "Crimson Leaf executive planning — boardroom deliberation, structured task breakdown, child task dispatch."
debug: true
system: agent_prompt
participant_prompt:
- "= identity.md"
agent_prompt:
- "= identity.md"
sections:
- agent
- project
- history
- rag
- participants
- participants_prompt
- roster
- templates
- message
- instructions
steps:
- type: think
rotate_participants: true
loop:
max_iterations: 3
hint: |
You are {agent.name}. This is round {task.iteration} of the Crimson Leaf planning session.
The executive board is breaking down this initiative into a concrete work plan.
Write YOUR perspective from your area of expertise:
- What work streams or tasks need to exist?
- What order must they happen in? What depends on what?
- Which agents from the TEAM ROSTER are best suited to each piece?
- What risks, gaps, or open questions do you see?
- What do you agree or disagree with from prior planning rounds?
CRIMSON LEAF CONTEXT:
Crimson Leaf is a holding company and incubator. It does NOT produce consumer deliverables.
Valid work for CL includes: market research, corporate architecture, executive recruitment,
portfolio governance, charter design, template authoring, and company incubation.
Reference these TASK TYPES when recommending work:
hire_agent — recruit a new agent to the CL roster
write_template — create or refine a PAE-Lang template
create_company — incubate a new sovereign Tenant
planning — sub-planning session for complex initiatives
boardroom — multi-agent deliberation on strategic decisions
research_plus — deep research with web search
analysis — data or situation analysis
quick — short single-step response
Be specific about agent assignments — use EXACT names from the TEAM ROSTER.
When the group has genuinely agreed on a complete plan, include exactly:
"consensus_reached: true"
If the plan still has gaps or unresolved assignments, do NOT include that line.
- type: think
agent: first_available
hint: |
Structure the team's agreed plan into a precise task list.
IMPORTANT: Do NOT re-deliberate or reconsider what was agreed above.
Your only job is to serialize the decisions into clean task records.
For each task:
- task_name: short, specific
- description: full detail — enough that the assigned agent can execute without asking
- agents: EXACT name(s) from TEAM ROSTER
- task_type: MUST be one of the valid template names listed below
- priority: 1 (critical) to 5 (nice-to-have)
Order tasks correctly — blockers before dependents.
No ambiguous assignments. No placeholder names.
VALID TASK TYPES (use ONLY these exact strings):
hire_agent, write_template, create_company, planning, boardroom,
research_plus, analysis, quick
- type: package
packet_type: PlanningResponsePacket
schema:
tasks:
- task_name: "string — short descriptive name"
description: "string — full instructions for the assigned agent"
agents:
- "string — EXACT agent name from TEAM ROSTER"
task_type: "string — MUST be a template name from the valid list"
priority: "integer 1 (critical) to 5 (nice-to-have)"
insert_children: true
- type: close
rag_update: false
adjudication:
enabled: false

91
templates/write_template.yml Normal file
View File

@@ -0,0 +1,91 @@
name: write_template
description: "CEO designs a new PAE-Lang template — skills-guided, adjudicated, committed via AR."
debug: true
system: agent_prompt
agent_prompt:
- "= identity.md"
skills:
- guides/PAETemplateGuide.md
sections:
- agent
- project
- rag
- templates
- skills
- message
- rejection_feedback
- instructions
steps:
- type: think
hint: |
You are {agent.name}, designing a new operational template for the company.
CONTEXT: Read the SKILLS & GUIDES section — it contains the PAE Template Guide
which defines every YAML key, step type, section key, and constraint you must follow.
THE IRON RULE: NEVER mix thinking and formatting in the same LLM step.
A `think` step reasons freely. A `package` step serializes only.
If the template needs both reasoning and structured output, use two steps.
DESIGN PROCESS:
1. Review the AVAILABLE TASK TEMPLATES to check for overlap.
If an existing template already covers this need, explain why a new one is unnecessary.
2. If a new template IS justified, design it following the PAE Template Guide exactly.
TEMPLATE DESIGN REQUIREMENTS:
- name: must match the intended filename (lowercase_with_underscores, no .yml extension)
- description: one clear sentence explaining what this template does
- system: usually `agent_prompt` for full identity, or a builder for custom system prompts
- sections: ordered list of section keys — always include `message` and usually `instructions` last
- steps: at minimum one `think` step and a `close` step at the end
- adjudication: configure with appropriate criteria and threshold for the task type
CONSTRAINTS:
- The template must serve the company charter.
- Only use step types defined in the guide: think, package, document, spawn, reply, close, tool.
- Do NOT use process_ledger (AR-only).
- close must always be the last step.
- If the template needs skills injection, declare the skills: array at the top level.
- Variable interpolation: {agent.name}, {project.name}, {task.message}, {steps[N].text}, etc.
- type: package
packet_type: IntakeResponse
hint: |
Convert the template design into a strict JSON payload.
Output exactly ONE write_template action.
The template_yaml must be valid YAML that follows the PAE Template Guide.
Do not include prose outside the JSON structure.
schema:
actions:
- type: write_template
company_slug: "string — the company this template belongs to"
template_name: "string — the template name (must match name: key in YAML)"
template_yaml: "string — complete valid YAML content of the template file"
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 85
deliverable_type: coordination
criteria:
pae_lang_compliance:
weight: 30
description: "Template follows PAE-Lang specification — valid step types, sections, keys"
charter_alignment:
weight: 20
description: "Template serves the company charter and operational needs"
iron_rule:
weight: 20
description: "Think and package steps are properly separated — no mixed reasoning/formatting"
completeness:
weight: 15
description: "All required keys present, close step at end, sections properly ordered"
non_duplication:
weight: 15
description: "Template does not duplicate an existing template's purpose"