Sprint 81: update templates/project_index.yml
This commit is contained in:
@@ -1,93 +1,128 @@
|
|||||||
name: project_index
|
name: project_index
|
||||||
description: "Compiles a master MANUSCRIPT-README.md index of all project deliverables, revisions, and publication status."
|
description: "Compiles a master MANUSCRIPT-README.md index of all project deliverables, revisions, and publication status."
|
||||||
debug: true
|
debug: true
|
||||||
system: agent_prompt
|
system: agent_prompt
|
||||||
|
|
||||||
agent_prompt:
|
agent_prompt:
|
||||||
- "= identity.md"
|
- "= identity.md"
|
||||||
|
|
||||||
sections:
|
sections:
|
||||||
- agent
|
- agent
|
||||||
- project
|
- project
|
||||||
- deliverables
|
- deliverables
|
||||||
- message
|
- message
|
||||||
- instructions
|
- instructions
|
||||||
|
|
||||||
steps:
|
steps:
|
||||||
- type: think
|
- type: think
|
||||||
hint: |
|
hint: |
|
||||||
You are {agent.name}. Compile a comprehensive MANUSCRIPT-README.md for this project.
|
You are {agent.name}. Compile a comprehensive MANUSCRIPT-README.md for this project.
|
||||||
|
|
||||||
Look at the PROJECT DELIVERABLES section above -- it lists every file committed during this project.
|
Look at the PROJECT DELIVERABLES section above -- it lists every file committed during this project.
|
||||||
|
|
||||||
Write a well-structured README that includes:
|
Write a well-structured README that includes:
|
||||||
|
|
||||||
## [Book Title] -- Book 1
|
## [Book Title] -- Book 1
|
||||||
**[Company Name] | Author: [Lead Author] | Creative Director: [Creative Director]**
|
**[Company Name] | Author: [Lead Author] | Creative Director: [Creative Director]**
|
||||||
|
|
||||||
> [Opening hook line from Chapter 1]
|
> [Opening hook line from Chapter 1]
|
||||||
|
|
||||||
Brief pitch (2-3 sentences about the project's concept, genre, and target audience).
|
Brief pitch (2-3 sentences about the project's concept, genre, and target audience).
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Publication Status
|
## Publication Status
|
||||||
[Based on the editorial report in deliverables -- GO / NO-GO verdict, score if available, date]
|
[Based on the editorial report in deliverables -- GO / NO-GO verdict, score if available, date]
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Reading Order
|
## Reading Order
|
||||||
A table with columns: Chapter Number | Chapter Title | POV | File
|
A table with columns: Chapter Number | Chapter Title | POV | File
|
||||||
(Pull from the final-chapter-*.md files in deliverables)
|
(Pull from the final-chapter-*.md files in deliverables)
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Chapter Continuity Chain
|
## Chapter Continuity Chain
|
||||||
A table showing how each chapter connects to the next:
|
A table showing how each chapter connects to the next:
|
||||||
Transition | Previous chapter ends... | Next chapter opens...
|
Transition | Previous chapter ends... | Next chapter opens...
|
||||||
(Pull quotes from the actual chapter files)
|
(Pull quotes from the actual chapter files)
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Revisions Applied
|
## Revisions Applied
|
||||||
If any revise-*.md files exist in deliverables, list them with what was revised.
|
If any revise-*.md files exist in deliverables, list them with what was revised.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Research & Planning Documents
|
## Research & Planning Documents
|
||||||
List all non-chapter deliverables (outline, trend report, editorial report, launch strategy, etc.)
|
List all non-chapter deliverables (outline, trend report, editorial report, launch strategy, etc.)
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Team
|
## Team
|
||||||
A table of agents, roles, and contributions based on the project context.
|
A table of agents, roles, and contributions based on the project context.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Iteration History
|
## Iteration History
|
||||||
If earlier draft files exist (write-chapter-*, rewrite-chapter-*, etc.), note them briefly.
|
If earlier draft files exist (write-chapter-*, rewrite-chapter-*, etc.), note them briefly.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
*Generated by [Company Name] AI team | PAE Multi-Agent System*
|
*Generated by [Company Name] AI team | PAE Multi-Agent System*
|
||||||
|
|
||||||
- type: document
|
- type: document
|
||||||
filename: "MANUSCRIPT-README"
|
filename: "MANUSCRIPT-README"
|
||||||
|
|
||||||
- type: close
|
# Sprint 81 Loop 2: when a book is complete, automatically dispatch a marketing campaign
|
||||||
rag_update: true
|
# to Crimson Leaf Marketing. optional: true so that if dispatch fails, the book is still done.
|
||||||
|
- type: tool
|
||||||
adjudication:
|
action: enqueue_strategy
|
||||||
enabled: true
|
optional: true
|
||||||
pass_threshold: 65
|
params:
|
||||||
deliverable_type: coordination
|
company_slug: "crimson_leaf_marketing"
|
||||||
criteria:
|
project_slug: "book-marketing-agency"
|
||||||
completeness:
|
task_type: "marketing_campaign"
|
||||||
weight: 45
|
content: |
|
||||||
description: "All project deliverables are catalogued"
|
MARKETING CAMPAIGN REQUEST -- {project.name}
|
||||||
accuracy:
|
|
||||||
weight: 35
|
The manuscript for "{project.name}" is complete and ready for marketing.
|
||||||
description: "Details about deliverables and team are correct"
|
|
||||||
structure:
|
BOOK DETAILS:
|
||||||
weight: 20
|
Title: {project.name}
|
||||||
description: "Index is well-organized and navigable"
|
Genre: {genre_name}
|
||||||
|
Audience: {genre_audience}
|
||||||
|
Author: {lead_author}
|
||||||
|
Company: Crimson Leaf Publishing
|
||||||
|
|
||||||
|
The MANUSCRIPT-README is available in the Crimson Leaf Publishing Gitea repository
|
||||||
|
under the {project.name} project deliverables. It contains the full reading order,
|
||||||
|
chapter summaries, continuity chain, and editorial verdict.
|
||||||
|
|
||||||
|
Please launch a full marketing campaign including:
|
||||||
|
- Campaign strategy (target platforms, timeline, budget allocation)
|
||||||
|
- Social media content pack (TikTok, Instagram, Facebook)
|
||||||
|
- Email campaign (reader list announcement)
|
||||||
|
- Press release (book announcement)
|
||||||
|
- Ad copy (platform-specific variations)
|
||||||
|
- Author bio update
|
||||||
|
|
||||||
|
MISSION: Get this book discovered by its audience and generate revenue for Crimson Leaf.
|
||||||
|
|
||||||
|
- type: close
|
||||||
|
rag_update: true
|
||||||
|
|
||||||
|
adjudication:
|
||||||
|
enabled: true
|
||||||
|
pass_threshold: 65
|
||||||
|
deliverable_type: coordination
|
||||||
|
criteria:
|
||||||
|
completeness:
|
||||||
|
weight: 45
|
||||||
|
description: "All project deliverables are catalogued"
|
||||||
|
accuracy:
|
||||||
|
weight: 35
|
||||||
|
description: "Details about deliverables and team are correct"
|
||||||
|
structure:
|
||||||
|
weight: 20
|
||||||
|
description: "Index is well-organized and navigable"
|
||||||
|
|||||||
Reference in New Issue
Block a user