feat(clp): build full CLP agent roster, templates, and skills library

- 8 company agents: Lyra (intake), Selene (CEO), Atlas (research),
  Nova (publishing ops), Iris (author), Devon (dev editor),
  Lane (line editor), Cora (continuity editor)
- 19 additional templates (20 total): blog, recipe, short_story,
  book pipeline, ai_article, planning, boardroom, quick, project_index
- 5 skill guides: YA, Romance, SciFi, Blog, Recipe writing
- Rewritten charter and business plan

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Baity
2026-03-12 01:14:51 -04:00
parent d6b2c94135
commit 50749f8e2b
52 changed files with 3276 additions and 63 deletions

View File

@@ -0,0 +1,97 @@
name: recipe_collection_plan
description: "Plan a themed recipe collection and spawn individual recipe_develop tasks for Iris."
debug: true
system: agent_prompt
agent_prompt:
- "= identity.md"
- "agent.rag.json"
sections:
- agent
- project
- history
- rag
- deliverables
- message
- instructions
steps:
- type: think
hint: |
You are planning a recipe collection for the project described above.
Read the project description and current message to understand the collection theme,
cuisine type, target audience, and any constraints.
Design a COMPLETE COLLECTION PLAN. Structure it as:
## Collection Title
[A compelling, specific title for the full collection]
## Collection Brief
[23 sentences: who this is for, what culinary territory it covers, what makes it distinct]
## Recipes
For each recipe (aim for 812 recipes per collection unless specified otherwise):
### [Recipe N]: [Recipe Name]
- **Concept**: One sentence on the dish — what it is and why it belongs in this collection
- **Unique angle**: What makes this version special (technique, ingredient, twist)
- **Difficulty**: Easy / Medium / Hard
- **Occasion**: When would someone cook this?
- **Brief for Iris**: 23 sentences describing exactly what to develop. Include any
specific requirements (e.g., "must be vegan", "uses [key ingredient]", "under 30 minutes").
Ensure variety across:
- Difficulty levels (mix of easy, medium, and one or two harder recipes)
- Meal types (appetizers, mains, sides, desserts if appropriate)
- Time commitment (some quick, some weekend projects)
- Dietary options (include at least one vegetarian or vegan option)
- type: document
filename: "{{task_name_slug}}-collection-plan"
- type: package
packet_type: IntakeResponse
hint: |
Convert every recipe from the collection plan above into a create_task action for Iris.
RULES:
- One action per recipe
- task_name: "Develop Recipe N: [Recipe Name]" where N is 1, 2, 3...
- agent_name: "Iris"
- task_type: "recipe_develop"
- description: Full brief for this recipe. Start with:
"You are developing Recipe N: [Recipe Name] for the [Collection Title] collection.
[Concept]. [Unique angle]. [Occasion].
[The full 'Brief for Iris' text from the plan above.]"
- depends_on: "" (all recipes can be developed in parallel)
Produce one action per recipe. No prose.
schema:
actions:
- type: create_task
task_name: "string"
agent_name: "string"
task_type: "recipe_develop"
description: "string"
depends_on: "string"
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 65
deliverable_type: coordination
criteria:
completeness:
weight: 40
description: "All recipes fully defined with clear briefs for execution"
variety:
weight: 35
description: "Collection has good range across difficulty, meal type, and dietary options"
coherence:
weight: 25
description: "Recipes feel like a unified collection with a clear culinary identity"