docs(changeset): cover full compound-engineering workflow integration
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -4,8 +4,7 @@
|
||||
|
||||
Make the built-in compound-engineering workflow run the CE way end-to-end:
|
||||
|
||||
- The execute stage now invokes the `compound-engineering:ce-work` skill in coding mode instead of the generic executor prompt.
|
||||
- Workflow-step sessions now carry a `FUSION_WORKFLOW_STEP` signal so skills know they are running autonomously (no synchronous question tool) and surface user questions via the await-input convention instead of a blocking prompt with no listener.
|
||||
- The plugin now bundles the `ce-commit`, `ce-commit-push-pr`, and `ce-resolve-pr-feedback` skills, enabling the CE commit/PR/resolve-feedback merge flow.
|
||||
|
||||
(Further stages — wiring the planning-question pause + task-card answer loop, the CE merge flow, and subagent persona support — land in follow-up commits on this feature.)
|
||||
- **Execute** stage invokes the `compound-engineering:ce-work` skill in coding mode instead of the generic executor prompt.
|
||||
- **Merge** stage adds `ce-commit-push-pr` and `ce-resolve-pr-feedback` skill steps (CE owns commit/push/PR + feedback; Fusion's merge seam still owns the board-state merge). The plugin now bundles `ce-commit`, `ce-commit-push-pr`, and `ce-resolve-pr-feedback`.
|
||||
- **Planning questions reach a human:** workflow-step sessions carry a `FUSION_WORKFLOW_STEP` signal; in that mode the CE skills emit an await-input sentinel instead of calling a blocking tool with no listener. The executor parks the task `awaiting-user-input` with the question, and a new task-card **"Answer questions"** button opens the workflow tab where the existing input banner captures the answer and resumes the step.
|
||||
- **Subagents work in workflow steps:** `fn_spawn_agent` gains an optional `systemPromptOverride`; the plugin installs the 43 `ce-*` persona definitions plugin-locally and exposes their directory via `FUSION_CE_AGENTS_DIR`, so the CE skills read a persona def and spawn it as a real subagent (falling back to inline single-agent work when unavailable).
|
||||
|
||||
Reference in New Issue
Block a user