172ce3a0e1
Agents: Peter (CEO), David (CTO), Sarah (Market Intel), Elena (Ops Architect) Templates: market_research, company_design, design_review, design_roundtable, design_polish, bootstrap_company RAG: business_plan.md, core_directives.md (5 immutable directives) Pipeline: 6-phase incubation protocol with dependency chain and kill conditions Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
77 lines
2.5 KiB
YAML
77 lines
2.5 KiB
YAML
name: design_polish
|
|
description: >
|
|
Refine the company design specification based on board review consensus.
|
|
Produces the final, bootstrap-ready design document.
|
|
model: power
|
|
|
|
sections:
|
|
- agent
|
|
- project
|
|
- rag
|
|
- deliverables
|
|
- message
|
|
- instructions
|
|
|
|
steps:
|
|
- type: think
|
|
hint: |
|
|
You are Elena, Chief Operations Architect at Crimson Leaf LLC.
|
|
|
|
The board has completed their independent reviews and reached consensus
|
|
in the design roundtable. Your job is to produce the FINAL company design
|
|
specification incorporating all approved changes.
|
|
|
|
BOARD CONSENSUS:
|
|
{consensus_critique}
|
|
|
|
KEY CHANGES REQUIRED:
|
|
{key_changes}
|
|
|
|
DESIGN VERDICT: {design_verdict}
|
|
|
|
Peter (CEO): {peter_final}
|
|
David (CTO): {david_final}
|
|
Sarah (Market Intelligence): {sarah_final}
|
|
|
|
ORIGINAL DESIGN SPECIFICATION:
|
|
{design_spec}
|
|
|
|
INSTRUCTIONS:
|
|
1. Address every item in KEY CHANGES REQUIRED. Do not skip any.
|
|
2. Preserve everything the board marked as STRENGTHS.
|
|
3. Do not add new agents, templates, or pipeline steps that weren't discussed.
|
|
4. If a change conflicts with another, follow Peter's direction (CEO authority).
|
|
5. The output must be a COMPLETE, self-contained design specification with
|
|
all sections present — not a diff or changelog.
|
|
|
|
OUTPUT FORMAT (exact sections required):
|
|
1. EXECUTIVE SUMMARY — Company name, slug, one-paragraph mission
|
|
2. MARKET JUSTIFICATION — Why this company, why now
|
|
3. AGENT ROSTER — Table: Name | Role | Title | Department | Responsibility
|
|
4. CHAIN OF COMMAND — Who manages whom
|
|
5. TEMPLATE STACK — Exact list of templates to procure
|
|
6. PIPELINE SOP — Numbered steps: task_type, agent, depends_on
|
|
7. REVENUE MODEL — How the company makes money
|
|
8. SUCCESS METRICS — 30/60/90 day targets
|
|
9. RISKS & MITIGATIONS — Top 3 risks with mitigations
|
|
10. BOARD APPROVAL — "APPROVED FOR BOOTSTRAP" with date
|
|
|
|
- type: document
|
|
filename: "company-design-final-{{task_name_slug}}"
|
|
|
|
- type: package
|
|
hint: |
|
|
The polished design is complete. Spawn the bootstrap task to create the company.
|
|
schema:
|
|
design_approved: boolean
|
|
spawn:
|
|
- task_type: bootstrap_company
|
|
task_name: "Bootstrap: {task.message}"
|
|
agent_name: David
|
|
priority: 8
|
|
depends_on:
|
|
- "Polish Design: {task.message}"
|
|
|
|
- type: close
|
|
rag_update: true
|