uncaged/workflow
10
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: remove per-role extractPrompt from RoleDefinition #174

New Issue
Closed
opened 2026-05-11 07:25:20 +00:00 by xiaoju · 1 comment
xiaoju commented 2026-05-11 07:25:20 +00:00
Owner
Copy Link
Copy Source

What

Remove the extractPrompt field from RoleDefinition. Replace with a single hardcoded generic extraction prompt in the extract pipeline.

Why

Each role's extractPrompt is redundant:

  • The role's systemPrompt already dictates the agent's output format
  • The Zod schema (exposed as function tool parameters) already fully describes what to extract
  • The extract LLM system prompt already says 'call the tool with JSON arguments matching the schema'
  • All existing extractPrompt values are just paraphrasing the schema field names

A single generic prompt is sufficient for all roles.

Changes

  1. workflow-protocol — remove extractPrompt from RoleDefinition type
  2. workflow-runtime — update re-exported types
  3. workflow-execute/extract — use a hardcoded generic prompt instead of role.extractPrompt
  4. workflow-template-develop — remove extractPrompt from all 5 roles
  5. workflow-template-solve-issue — remove extractPrompt from preparer and submitter
  6. cli-workflow — update init templates and skill output
  7. Coder role — move 'use last finished phase hash' hint into z.string().describe()

Breaking change — bundle authors must remove extractPrompt from role definitions.

— xiaoju (NEKO Team)

## What Remove the extractPrompt field from RoleDefinition. Replace with a single hardcoded generic extraction prompt in the extract pipeline. ## Why Each role's extractPrompt is redundant: - The role's systemPrompt already dictates the agent's output format - The Zod schema (exposed as function tool parameters) already fully describes what to extract - The extract LLM system prompt already says 'call the tool with JSON arguments matching the schema' - All existing extractPrompt values are just paraphrasing the schema field names A single generic prompt is sufficient for all roles. ## Changes 1. workflow-protocol — remove extractPrompt from RoleDefinition type 2. workflow-runtime — update re-exported types 3. workflow-execute/extract — use a hardcoded generic prompt instead of role.extractPrompt 4. workflow-template-develop — remove extractPrompt from all 5 roles 5. workflow-template-solve-issue — remove extractPrompt from preparer and submitter 6. cli-workflow — update init templates and skill output 7. Coder role — move 'use last finished phase hash' hint into z.string().describe() Breaking change — bundle authors must remove extractPrompt from role definitions. — xiaoju (NEKO Team)
xiaoju commented 2026-05-11 07:27:15 +00:00
Author
Owner
Copy Link
Copy Source

Phase 拆分

Phase 1: 类型定义 + extract 管线

  • 从 RoleDefinition 删除 extractPrompt
  • extract 管线改用硬编码通用 prompt
  • coder role 的提示迁移到 schema .describe()
  • Testing issue: 待创建

Phase 2: 模板 + CLI + skill

  • 两个 workflow template 删除所有 extractPrompt
  • CLI init 模板更新
  • skill 输出更新
  • Testing issue: 待创建

— 小橘 🍊（NEKO Team）

## Phase 拆分 ### Phase 1: 类型定义 + extract 管线 - 从 `RoleDefinition` 删除 `extractPrompt` - extract 管线改用硬编码通用 prompt - coder role 的提示迁移到 schema `.describe()` - Testing issue: 待创建 ### Phase 2: 模板 + CLI + skill - 两个 workflow template 删除所有 `extractPrompt` - CLI init 模板更新 - skill 输出更新 - Testing issue: 待创建 — 小橘 🍊（NEKO Team）
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
aobing jiashuang (Jia Shuang) jiayi (Jiayi) luming scottwei tuanzi xiaoju xiaomo xiaonuo xingyue
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: uncaged/workflow#174
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?