External Handoff

外部交付物

🎯 Prototype Handoff

用于将圆桌结论转换为工具无关的 prototype-handoff.md,并按需生成 Pencil 或 Lovable 适配产物。

markdown
# Prototype Handoff

<!-- meta -->
- handoff_version: "1.0"
- generated_by: roundtable
- prototype_target: pencil
<!-- /meta -->

## Target
- Prototype Target: pencil
- Goal: 快速验证产品形态 / 输出可评审设计稿 / 进入后续实现
- Delivery Mode: draft | reviewable | implementation-ready

## Product Goal
用一句话说明要构建什么,以及它解决谁的什么问题。

## Target Users
- 用户角色:
- 核心场景:
- 成功标准:

## Core User Flow
1. 用户进入:
2. 用户完成:
3. 系统反馈:
4. 用户下一步:

## Pages
### Page: 页面名称
- Purpose:
- Main Components:
- Primary Actions:
- Empty State:
- Loading State:
- Error State:
- Mobile Behavior:

## Data Model
| Entity | Fields | Relationships | Validation |
|:---|:---|:---|:---|
| Example | id, name, status | belongs_to user | name required |

## Adapter Notes
- Workspace Reference:
- Export Requirements:
- Compression Strategy:
- Design System Source:
- Design Intelligence Source: none | ui-ux-pro-max | manual

## Acceptance Criteria
> 每项验收标准必须使用 - [ ] AC-xxx: 前缀,供 tasks.acceptance_refs 精确引用。

- [ ] AC-001: 用户可以完成核心路径
- [ ] AC-002: 所有表单有校验和错误提示
- [ ] AC-003: 移动端布局不溢出
- [ ] AC-004: 空状态、加载态、错误态完整

🧾 Core JSON Contracts

v1.1 补齐审计时间戳、可追踪决策时间、机器可读验收引用和 agent owner 命名空间。

markdown
# Core JSON Contract

## report.json
{
  "report_version": "1.0",
  "roundtable_status": "ready_for_execution",
  "artifact_refs": {
    "context_pack": "docs/roundtable/.../context-pack.json",
    "decisions": "docs/roundtable/.../decisions.json",
    "tasks": "docs/roundtable/.../tasks.json",
    "prototype_handoff": "docs/roundtable/.../prototype-handoff.md",
    "execution_context": "docs/roundtable/.../execution-context.json",
    "execution_plan": "docs/roundtable/.../execution-plan.md",
    "execution_log": "docs/roundtable/.../execution-log.md",
    "execution_review": ""
  },
  "generated_at": "ISO8601",
  "last_updated_at": "ISO8601"
}

Rule: artifact_refs.execution_review is empty unless execution_result_state = executed_reviewed.

## decisions.json
{
  "decision_log_version": "1.0",
  "decisions": [
    {
      "decision_id": "D-001",
      "status": "accepted",
      "owner": "product",
      "approval_required": false,
      "approved_at": "",
      "decided_at": "ISO8601"
    }
  ]
}

## tasks.json
{
  "task_plan_version": "1.0",
  "tasks": [
    {
      "task_id": "T-001",
      "owner": "agent:pencil-runner",
      "acceptance_refs": ["prototype-handoff.md#AC-001"],
      "artifact_refs": ["prototype-handoff.md"],
      "decision_refs": ["D-001"]
    }
  ]
}

Validation Categories

prototype-review.json 的 checks[].category 必须使用固定枚举,便于后续聚合验证结果。

markdown
# Prototype Review Contract

## prototype-review.json
{
  "handoff_ref": "docs/roundtable/.../prototype-handoff.md",
  "handoff_version": "1.0",
  "implementation_ref": "pencil export or lovable output",
  "status": "passed | failed | partial | needs_info | needs_migration",
  "checks": [
    {
      "check_id": "PT-001",
      "category": "pages",
      "expected": "Dashboard page exists",
      "actual": "Dashboard page implemented",
      "status": "passed"
    }
  ]
}

## Allowed check categories
- pages
- flow
- permissions
- states
- responsive
- design
- ui_ux
- execution
- feasibility

Superpowers Execution Adapter

v1.3 将 Superpowers 定义为独立执行适配器,并用 execution_result_state 区分静态计划、真实执行和已复盘执行。

markdown
# Superpowers Execution Adapter

## Complexity-aware activation
| complexity_level | Policy |
|:---|:---|
| light | never auto-enable |
| mini | recommend when implementation or validation is non-trivial |
| standard | default for implementation flows |
| full | always record execution_method_selection; default for implementation flows |

## execution-context.json
{
  "execution_context_version": "1.0",
  "execution_adapter": "superpowers",
  "execution_adapter_status": "enabled | disabled_by_user | disabled_by_policy | skipped_non_implementation | unavailable | static_plan",
  "execution_result_state": "not_executed | executed_unverified | executed_reviewed",
  "recommended_superpowers": ["superpowers:executing-plans"],
  "source_artifacts": {
    "decisions": "docs/roundtable/.../decisions.json",
    "tasks": "docs/roundtable/.../tasks.json",
    "validation_plan": "docs/roundtable/.../validation-plan.md",
    "prototype_handoff": "docs/roundtable/.../prototype-handoff.md"
  },
  "brainstorm_scope": "execution_only",
  "selection_reason": "complexity_policy | explicit_user_request | disabled_by_user | non_implementation_flow"
}

## Conditional artifacts
docs/roundtable/YYYY-MM-DD_topic-slug/
├── execution-context.json
├── execution-plan.md
├── execution-log.md
└── execution-review.md   # only when execution_result_state = executed_reviewed

Boundary:
- Superpowers may split plans, delegate subtasks, track execution, and review validation.
- It must not change decisions.json semantics, product scope, permission rules, acceptance criteria, or human approval gates.
- Static plans use execution_result_state = not_executed and must not generate execution-review.md.

🧩 Platform Adapter Package

v1.3 新增 Codex、Claude Code、Trae 三端薄入口,以及 new-archive / validate-json 自动化脚本。

markdown
# Platform Adapter Package

roundtable/
├── SKILL.md
├── manifest.json
├── roundtable.config.json
├── codex/AGENTS-snippet.md
├── claude/CLAUDE-snippet.md
├── claude/commands/roundtable.md
├── trae/project_rules.md
├── trae/custom-agent-prompt.md
└── scripts/
    ├── new-archive.mjs
    ├── validate-json.mjs
    └── validate-execution-context.mjs

Rules:
- All platforms point to roundtable/SKILL.md.
- Platform adapters are thin entry points, not protocol forks.
- validate-json.mjs checks artifact_refs, acceptance_refs, and execution-review state rules.

📈 Diagram Artifacts

--draw 是 MVP 后增强;v1.1 先固定归档路径,避免后续实现各自定义图表位置。

markdown
# Diagrams Generated

docs/roundtable/YYYY-MM-DD_topic-slug/
└── diagrams/
    ├── flow.mmd
    ├── state-machine.mmd
    └── architecture.mmd

Rules:
- Generated only when --draw is enabled.
- Archive Mermaid source files only.
- Rendered PNG / SVG files are presentation outputs, not archive artifacts.

✏️ Pencil Adapter

Pencil 是 v1 默认原型目标。MVP 默认生成静态适配产物,不要求自动驱动 Pencil 完成设计生成。

markdown
# Pencil Adapter Artifacts

## pencil-prompt.md
- Product Goal
- Core User Flow
- Pages
- Permission Rules
- Design Direction
- Acceptance Criteria
- Required Exports

## pencil-task.json
{
  "target": "pencil",
  "source_handoff": "docs/roundtable/YYYY-MM-DD_topic-slug/prototype-handoff.md",
  "deliverables": ["designs/<topic>.pen", "artifacts/<topic>.png"],
  "requirements": {
    "mobile_behavior_required": true,
    "empty_state_required": true,
    "error_state_required": true,
    "permission_boundary_required": true
  }
}

## pencil-runbook.md
- 输入文件路径
- 需要人工复制或导入到 Pencil 的内容
- 期望导出的文件类型
- 验证时应回填的 implementation_ref
- Pencil 能力不足时的降级说明

🎨 Design Intelligence Adapter

可选接入 ui-ux-pro-max-skill,用于增强设计系统、前端设计 brief 和 UI/UX review checklist;它只增强表达层,不改变 Roundtable 已裁决的业务语义。

markdown
# Design Intelligence Adapter

## Input from prototype-handoff.md
- Product Goal: 为客服团队提供反馈处理工作台
- Page: Feedback Dashboard
- Components: filters, feedback table, status tags, assignee column
- Permission Rules: 普通处理人仅看自己的反馈;管理员可查看和分派所有反馈
- Design Direction: 专业、可信、适合高频后台操作
- Design Intelligence Source: ui-ux-pro-max

## design-system-brief.md
- Visual language: Enterprise SaaS / operational dashboard
- Color direction: neutral slate base, cyan for navigation, amber for attention
- Typography: compact documentation-friendly sans, numeric columns use tabular figures
- Layout density: medium-high density for dashboard tables
- Motion: restrained transitions for filters, drawers, and validation feedback
- Accessibility: visible focus ring, AA contrast, keyboard reachable actions

## ui-ux-review-checklist.md
- [ ] Dashboard hierarchy separates filters, summary, and table
- [ ] Empty, loading, and error states exist
- [ ] Status colors are not the only indicator
- [ ] Detail drawer is keyboard reachable and closable
- [ ] 375px layout stacks filters and table cards
- [ ] Admin-only assignment respects permission rules

## frontend-design-brief.md
- Layout structure
- Component priorities
- Interaction states
- Implementation notes
- Links back to prototype-handoff.md

Boundary: this adapter may enhance Design Direction and UI quality checks, but must not change product scope, permissions, data model, API contract, or business acceptance criteria.

🔧 GitLab Handoff

用于将圆桌结论转换为 GitLab Issue 或 Merge Request。

markdown
# Title

## Background

## Decision

## Scope
### In Scope
### Out of Scope

## Tasks
- [ ] Task 1

## Acceptance Criteria
- [ ] AC-001: Criterion 1

## Risks

## References
- Roundtable report:
- Prototype handoff:

## GitLab Metadata
- GitLab Base URL: https://gitlab.asiainfo.com
- Project:
- Branch:
场景到交付物示例

这些示例展示同一套圆桌协议如何针对不同场景生成不同 handoff。

适用场景

客户反馈平台

把“做个平台”这种方向性表达,收敛成 MVP 页面、数据模型、权限边界和验收标准。

Prototype

  • Public Feedback Form
  • Admin Feedback Dashboard
  • Status History
  • Basic Analytics

GitLab

  • Task split for MVP pages
  • Permission boundary checklist
  • Acceptance criteria for state flow
/roundtable --prototype pencil --roles product,data,developer,qa

AI 客服辅助

把“接 AI”拆成能力边界、知识库范围、人工确认机制和风险控制要求。

Prototype

  • Agent suggestion panel
  • Knowledge confidence status
  • Manual approve-before-send flow

GitLab

  • Security checklist
  • Audit log tasks
  • Risk mitigation work items
/roundtable --roles product,security,architect,developer,qa

Prototype / Pencil 原型交付

把“先出原型”变成清晰页面、数据模型、权限规则和可验收 Prototype Handoff。

Prototype

  • Product Goal
  • Core User Flow
  • Pages
  • Permission Rules

GitLab

  • Follow-up implementation tasks
  • Validation checklist
  • Roundtable report references
/roundtable --prototype pencil --gitlab
交付物示例

这些不是完整文件,而是更接近真实输出形态的片段,帮助用户快速理解结果长什么样。

适用场景

客户反馈平台

把“做个平台”这种方向性表达,收敛成 MVP 页面、数据模型、权限边界和验收标准。

/roundtable --prototype pencil --roles product,data,developer,qa

Human Report

markdown
## 核心结论
- 先做提交、后台列表、状态流转、基础统计四条主路径
- 后台必须区分管理员与普通处理人
- 本轮不做复杂报表和多租户

Prototype Handoff 示例

markdown
## Product Goal
Build a customer feedback workflow for teams to collect, triage, and track feedback.

## Pages
- Public Feedback Form
- Admin Feedback Dashboard
- Feedback Detail
- Analytics Overview

GitLab Issue 示例

markdown
## Scope
### In Scope
- feedback form
- admin list and detail
- status history
- basic analytics

## Acceptance Criteria
- [ ] AC-001: Admin can update status
- [ ] AC-002: Status history is preserved

AI 客服辅助

把“接 AI”拆成能力边界、知识库范围、人工确认机制和风险控制要求。

/roundtable --roles product,security,architect,developer,qa

Human Report

markdown
## 决策摘要
- 首期做“建议回复”,不做“自动发送”
- 所有模型输出必须经过人工确认
- 仅允许访问脱敏知识库与授权 FAQ

Prototype Handoff 示例

markdown
## Core User Flow
1. Agent suggests a reply draft
2. Human reviewer checks confidence and citations
3. Reviewer edits or approves
4. System logs the final response

GitLab Issue 示例

markdown
## Risks
- hallucinated reply without evidence
- stale knowledge base
- missing audit trail

## Tasks
- [ ] add manual approval gate
- [ ] add audit logging

Prototype / Pencil 原型交付

把“先出原型”变成清晰页面、数据模型、权限规则和可验收 Prototype Handoff。

/roundtable --prototype pencil --gitlab

Human Report

markdown
## 结论
- 先做 MVP 原型,不直接进入正式开发
- 必须补齐空状态、错误态、权限规则
- 生成后要做一次和 handoff 对照验收

Prototype Handoff 示例

markdown
## Pages
- Workspace Dashboard
- Request Intake
- Expert Review Timeline
- Decision Summary

## Acceptance Criteria
- [ ] AC-001: core user flow is complete
- [ ] AC-002: mobile layout does not overflow

GitLab Issue 示例

markdown
## References
- Roundtable report
- Prototype handoff

## Acceptance Criteria
- [ ] AC-001: page coverage reviewed
- [ ] AC-002: permission rules verified
- [ ] AC-003: empty/error states reviewed

Lovable Compatibility URL

Lovable 在 v1 中是兼容适配器;主规格仍以 prototype-handoff.md 为准。

https://lovable.dev/?autosubmit=true#prompt=<URL_ENCODED_PROTOTYPE_PROMPT>