xiaoju
98122b446d
- StartStep gains parentState: string | null (from StartNodePayload) - buildAgentPrompt injects Parent Context section when parentState is set - CLI thread show outputs parentState (top-level) and childThread (per step) - 2 new prompt tests + thread show assertion updates Refs #197, #194 小橘 🍊（NEKO Team）
@uncaged/workflow-template-solve-issue
Reference solve-issue workflow template: prepare a repo, delegate implementation to the develop workflow, then submit (e.g. open a PR).
This package exports a pure WorkflowDefinition (solveIssueWorkflowDefinition). Workflow instantiation (createWorkflow(definition, binding)) and any role-specific agent wiring (for example delegating developer to workflowAsAgent("develop")) are done in the workflow instance layer.
Install
bun add @uncaged/workflow-template-solve-issue @uncaged/workflow zod
In this monorepo: workspace:* for this package and @uncaged/workflow.
Usage
import { createWorkflow } from "@uncaged/workflow";
import { solveIssueWorkflowDefinition } from "@uncaged/workflow-template-solve-issue";
const run = createWorkflow(solveIssueWorkflowDefinition, binding);
Roles
| Role | Purpose |
|---|---|
| preparer | Set up context / repo state for the issue |
| developer | Implementation; default runs the registered develop workflow as a sub-agent |
| submitter | Finalize and submit the outcome (e.g. PR) |
Also exported: preparerRole, developerRole, submitterRole and their Zod meta schemas, SolveIssueMeta, solveIssueRoles.
Moderator flow
- Start →
preparer - After preparer →
developer - After developer →
submitter - After submitter →
END
API overview
| Export | Description |
|---|---|
solveIssueWorkflowDefinition |
description, roles, solveIssueModerator |
solveIssueModerator |
Linear Moderator<SolveIssueMeta> |
buildSolveIssueDescriptor |
Descriptor helper for bundles |
SOLVE_ISSUE_WORKFLOW_DESCRIPTION |
Human-readable one-liner |