72 lines
2.2 KiB
YAML
72 lines
2.2 KiB
YAML
name: content_plan
|
|
description: "Generate a structured content plan for a Crimson Leaf company or project. Produces a prioritized list of content tasks with assignments and rationale."
|
|
debug: true
|
|
system: agent_prompt
|
|
|
|
agent_prompt:
|
|
- "= identity.md"
|
|
|
|
sections:
|
|
- agent
|
|
- project
|
|
- history
|
|
- rag
|
|
- message
|
|
- instructions
|
|
|
|
steps:
|
|
- type: think
|
|
hint: |
|
|
You are {agent.name}, producing a content plan for Crimson Leaf.
|
|
|
|
Based on the request and available context, generate a practical content production plan.
|
|
|
|
Your plan must include:
|
|
|
|
OBJECTIVE -- One sentence: what this content is for and who it serves.
|
|
|
|
CONTENT ITEMS -- A numbered list of specific content pieces to produce. For each item:
|
|
- Title or working name
|
|
- Content type (article, brief, report, script, outline, etc.)
|
|
- Target length (approximate word count or format)
|
|
- Primary purpose (inform, convert, build authority, entertain, etc.)
|
|
- Which agent or team should produce it
|
|
- Estimated priority (1=critical, 3=standard, 5=optional)
|
|
|
|
SEQUENCING -- In what order should items be produced and why?
|
|
|
|
DEPENDENCIES -- What information, research, or approvals are needed before production starts?
|
|
|
|
SUCCESS CRITERIA -- How will we know this content plan was effective?
|
|
|
|
Be specific. Vague content plans produce vague content.
|
|
Limit the plan to items that can realistically be executed within two weeks.
|
|
|
|
- type: package
|
|
packet_type: ContentPlanPacket
|
|
schema:
|
|
objective: "string"
|
|
content_items:
|
|
- title: "string"
|
|
content_type: "string"
|
|
target_length: "string"
|
|
purpose: "string"
|
|
assigned_to: "string"
|
|
priority: "integer 1-5"
|
|
sequencing_notes: "string"
|
|
dependencies: "string"
|
|
success_criteria: "string"
|
|
insert_children: false
|
|
|
|
- type: close
|
|
rag_update: true
|
|
|
|
adjudication:
|
|
enabled: true
|
|
pass_threshold: 65
|
|
criteria:
|
|
- "Plan includes a clear objective"
|
|
- "Each content item has title, type, and assignment"
|
|
- "Plan is specific to the request, not generic boilerplate"
|
|
- "Success criteria are measurable"
|