From e8bd420f4e0e3ab6d8311a1893ae1fc20c24ba62 Mon Sep 17 00:00:00 2001 From: Nova_2761 Date: Fri, 17 Apr 2026 20:37:28 +0000 Subject: [PATCH] Sprint 81: update templates/project_index.yml --- templates/project_index.yml | 221 +++++++++++++++++++++--------------- 1 file changed, 128 insertions(+), 93 deletions(-) diff --git a/templates/project_index.yml b/templates/project_index.yml index f3071f9a..19d23345 100644 --- a/templates/project_index.yml +++ b/templates/project_index.yml @@ -1,93 +1,128 @@ -name: project_index -description: "Compiles a master MANUSCRIPT-README.md index of all project deliverables, revisions, and publication status." -debug: true -system: agent_prompt - -agent_prompt: - - "= identity.md" - -sections: - - agent - - project - - deliverables - - message - - instructions - -steps: - - type: think - hint: | - 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. - - Write a well-structured README that includes: - - ## [Book Title] -- Book 1 - **[Company Name] | Author: [Lead Author] | Creative Director: [Creative Director]** - - > [Opening hook line from Chapter 1] - - Brief pitch (2-3 sentences about the project's concept, genre, and target audience). - - --- - - ## Publication Status - [Based on the editorial report in deliverables -- GO / NO-GO verdict, score if available, date] - - --- - - ## Reading Order - A table with columns: Chapter Number | Chapter Title | POV | File - (Pull from the final-chapter-*.md files in deliverables) - - --- - - ## Chapter Continuity Chain - A table showing how each chapter connects to the next: - Transition | Previous chapter ends... | Next chapter opens... - (Pull quotes from the actual chapter files) - - --- - - ## Revisions Applied - If any revise-*.md files exist in deliverables, list them with what was revised. - - --- - - ## Research & Planning Documents - List all non-chapter deliverables (outline, trend report, editorial report, launch strategy, etc.) - - --- - - ## Team - A table of agents, roles, and contributions based on the project context. - - --- - - ## Iteration History - If earlier draft files exist (write-chapter-*, rewrite-chapter-*, etc.), note them briefly. - - --- - - *Generated by [Company Name] AI team | PAE Multi-Agent System* - - - type: document - filename: "MANUSCRIPT-README" - - - 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" +name: project_index +description: "Compiles a master MANUSCRIPT-README.md index of all project deliverables, revisions, and publication status." +debug: true +system: agent_prompt + +agent_prompt: + - "= identity.md" + +sections: + - agent + - project + - deliverables + - message + - instructions + +steps: + - type: think + hint: | + 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. + + Write a well-structured README that includes: + + ## [Book Title] -- Book 1 + **[Company Name] | Author: [Lead Author] | Creative Director: [Creative Director]** + + > [Opening hook line from Chapter 1] + + Brief pitch (2-3 sentences about the project's concept, genre, and target audience). + + --- + + ## Publication Status + [Based on the editorial report in deliverables -- GO / NO-GO verdict, score if available, date] + + --- + + ## Reading Order + A table with columns: Chapter Number | Chapter Title | POV | File + (Pull from the final-chapter-*.md files in deliverables) + + --- + + ## Chapter Continuity Chain + A table showing how each chapter connects to the next: + Transition | Previous chapter ends... | Next chapter opens... + (Pull quotes from the actual chapter files) + + --- + + ## Revisions Applied + If any revise-*.md files exist in deliverables, list them with what was revised. + + --- + + ## Research & Planning Documents + List all non-chapter deliverables (outline, trend report, editorial report, launch strategy, etc.) + + --- + + ## Team + A table of agents, roles, and contributions based on the project context. + + --- + + ## Iteration History + If earlier draft files exist (write-chapter-*, rewrite-chapter-*, etc.), note them briefly. + + --- + + *Generated by [Company Name] AI team | PAE Multi-Agent System* + + - type: document + filename: "MANUSCRIPT-README" + + # Sprint 81 Loop 2: when a book is complete, automatically dispatch a marketing campaign + # to Crimson Leaf Marketing. optional: true so that if dispatch fails, the book is still done. + - type: tool + action: enqueue_strategy + optional: true + params: + company_slug: "crimson_leaf_marketing" + project_slug: "book-marketing-agency" + task_type: "marketing_campaign" + content: | + MARKETING CAMPAIGN REQUEST -- {project.name} + + The manuscript for "{project.name}" is complete and ready for marketing. + + BOOK DETAILS: + Title: {project.name} + 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"