You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: update version to 2.0.31 and enhance prompt templates
- Bump package version to 2.0.31 in package.json and package-lock.json.
- Refine the needs-bot-review prompt template for clearer instructions.
- Improve the ready prompt template to provide better guidance for implementation.
- Add normalization for todo comment body input to handle escaped newline sequences.
- Enhance error handling in release-utils.js for file removal.
- Implement SQLite workspace hydration logic in cockpitManager.ts to ensure proper task and board hydration.
- Introduce tests for new functionality, including SQLite hydration and comment normalization.
Co-authored-by: Copilot <copilot@github.com>
copilotCockpitPromptSummary: "Route through canonical workflow flags, preserve approval checkpoints, and verify linked scheduler state before changing live scheduled cards."
8
+
copilotCockpitPromptSummary: "Route through canonical workflow flags, preserve approval checkpoints, verify linked scheduler state before changing live scheduled cards, and for needs-bot-review return plain text with short titled sections, bullets, and a compact recommendation."
@@ -58,6 +58,11 @@ This router skill is MCP-dependent. It must not attempt live routing or schedule
58
58
-`ON-SCHEDULE-LIST` → manage the linked scheduler job lifecycle for live scheduled cards.
59
59
-`needs-user-review` or `new` → keep the card active and route it for follow-up instead of scheduling immediately.
60
60
61
+
For `needs-bot-review` comments intended for direct Todo writeback:
62
+
63
+
- Return plain text with real line breaks, short titled sections, compact bullets, and a final `Recommendation:` block.
64
+
- Do not emit JSON payloads or literal escaped newline sequences such as `\n`.
65
+
61
66
## Example Set Requests
62
67
63
68
When the user asks for a demo/example set across surfaces, route it as separate artifacts instead of collapsing everything into scheduled tasks.
@@ -125,7 +130,8 @@ The current live dispatcher source contains two different `needs-bot-review` beh
125
130
- If `scheduler_remove_task` or `scheduler_get_task` shows that the linked task is already gone, clear the Cockpit card's `taskId` instead of leaving a stale link behind.
126
131
- Use flags for routing and review-state handoff. Keep the built-in `ON-SCHEDULE-LIST` flag when the card still represents a live scheduled item.
127
132
- When implementation is complete but the user still needs to review the result, prefer an existing review-state flag such as `needs-user-review`, and move the card only if the requested review section actually exists.
128
-
- Add one compact Cockpit comment that covers changes, validation, and remaining follow-up instead of scattering multiple status comments.
133
+
- For ready-path execution closeout, always write back exactly one compact Todo comment covering implementation changes, validation, and remaining follow-up before or together with the workflow-state update.
134
+
- Do not scatter multiple status comments for the same ready execution closeout.
129
135
130
136
## Suggested Update Format
131
137
@@ -155,4 +161,8 @@ Avoid output such as `Add flags: on-schedule-list, scheduled-task` because it mi
155
161
156
162
## Output Expectations
157
163
158
-
Return only the compact execution summary requested by the dispatcher flow. Avoid board dumps and avoid re-deriving routing state from the full board payload when `cockpit_list_routing_cards` already gives the candidate set.
164
+
Return only the compact execution summary requested by the dispatcher flow. Avoid board dumps and avoid re-deriving routing state from the full board payload when `cockpit_list_routing_cards` already gives the candidate set.
165
+
166
+
When the flow asks for a direct Todo review comment, keep the output readable as pasted text: short titled sections, concise bullets, and one compact closing recommendation.
167
+
168
+
When the flow is a ready execution closeout, include the single compact Todo comment needed for direct writeback so the Todo does not move state without a comment trail.
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -181,7 +181,9 @@ Start with one recurring loop that produces useful work instead of toy output.
181
181
-`Delivery Risk and Security Watch (Daily)` looks for shipping, trust, and operational blind spots.
182
182
-`Knowledge and Shipping Packager (Daily)` stages reusable docs, memory candidates, and release material for later curation.
183
183
-`Project Intelligence and Delivery Prep` runs those steps in sequence and stops at a review checkpoint before anything turns into real execution.
184
-
-`Onboarding Example Coverage Research` benchmarks whether the docs still explain Cockpit, Tasks, Jobs, and Research with explicit review checkpoints.
184
+
-`Onboarding Example Coverage Research` starts with a Todo Cockpit intake item, uses Research to gather or benchmark onboarding evidence, and then promotes approved follow-up into Tasks or Jobs.
185
+
186
+
Use that onboarding example when you want one concrete loop to demonstrate the product: start in Todo Cockpit, gather context with Research, promote approved work into Tasks or Jobs, and stop at a review checkpoint before autonomy expands.
185
187
186
188
This is a good fit for a solo product, an internal tool, a small SaaS, or an actively maintained extension like this repo.
Copy file name to clipboardExpand all lines: docs/feature-tour.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,6 +94,8 @@ Caption: Improve against a benchmark, not by guesswork.
94
94
95
95
Research can also act as a collaborative discovery phase before implementation: gather web knowledge, review the findings with the user, refine the direction, and only then turn the result into scheduled execution.
96
96
97
+
For onboarding, `Onboarding Example Coverage Research` shows the full loop in one pass: capture the gap in Todo Cockpit, use Research to benchmark the docs, promote approved fixes into Tasks or Jobs, and pause at a review checkpoint before broader autonomy.
98
+
97
99
Best for: prompt or workflow improvement that should be measured, not guessed.
Copy file name to clipboardExpand all lines: docs/getting-started.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,8 @@ Skip toy prompts. Start with one recurring loop that would still be worth keepin
39
39
- For a company team, use the same pattern for product signals, security and release readiness, support queues, or operations follow-up.
40
40
- If you also want to show the Research surface, add one benchmarked profile that scores onboarding or prompt quality against a simple command before you promote anything into execution.
41
41
42
+
`Onboarding Example Coverage Research` is the simplest version of that pattern: log the onboarding gap in Todo Cockpit, use Research to gather examples or benchmark the docs, then turn the approved next step into Tasks for a direct doc pass or Jobs for a staged follow-up. Use it when you want a real onboarding loop that still stops at a review checkpoint before autonomy expands.
43
+
42
44
That keeps the demo honest: the proof is useful output plus explicit review, not a claim that the system should run unchecked.
Copy file name to clipboardExpand all lines: package.json
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
"name": "copilot-cockpit",
3
3
"displayName": "Copilot Cockpit",
4
4
"description": "One VS Code system for AI planning and triage, execution and scheduling, and optional control-plane integration",
5
-
"version": "2.0.29",
5
+
"version": "2.0.31",
6
6
"publisher": "local-dev",
7
7
"license": "SEE LICENSE IN LICENSE",
8
8
"icon": "images/icon.png",
@@ -248,7 +248,7 @@
248
248
},
249
249
"copilotCockpit.needsBotReviewPromptTemplate": {
250
250
"type": "string",
251
-
"default": "You are handling a Todo that just entered needs-bot-review.\n\n{{todo_context}}\n\n{{mcp_skill_guidance}}\n\nResearch what is needed to review this item, identify missing context and risks, and return a plan-only response. If the request is clear, provide two concrete implementation options or one blocking clarification when the ambiguity is material.",
251
+
"default": "You are handling a Todo that just entered needs-bot-review.\n\n{{todo_context}}\n\n{{mcp_skill_guidance}}\n\nResearch what is needed to review this item using available tools and web search.\nReturn a plain-text review comment ready for direct Todo writeback with short titled sections and bullets:\nReview Summary:\n- 1-2 bullets on the request and current repo state\nRisks / Gaps:\n- bullets for missing context, risks, or unclear assumptions\nRecommendation:\n- one compact next step or blocking clarification; if the request is already clear, give two implementation options instead\nUse real line breaks. Do not emit JSON or escaped newline sequences such as \\n.\nWhen the review is complete, add that comment to this Todo using the cockpit MCP tools and set the flag to needs-user-review.",
"default": "You are preparing the execution artifact for a Todo that is now ready.\n\n{{todo_context}}\n\n{{mcp_skill_guidance}}\n\nCreate or refine the execution-ready handoff for this Todo. Preserve the user's actual requested work, keep unresolved questions explicit, and prefer existing repo-local skills and MCP tools over ad-hoc file edits when those tools are available.",
283
+
"default": "You are handling a Todo that is now ready for implementation.\n\n{{todo_context}}\n\n{{mcp_skill_guidance}}\n\nAnalyze this Todo using the Todo Cockpit skill and implement what the user decided in the last comment or the latest bot recommendation.\nIf there is no recent user comment, proceed with the bot's recommendation.\nAdd one compact Todo comment covering implementation changes, validation, and any remaining follow-up before or as you update the Todo to the correct workflow state.\nCheck the cockpit-todo-agent and cockpit-scheduler-router skills to determine the correct post-implementation state, and tell the user whether that guidance was found.\nIf the expected post-implementation state is not documented in the skills, add it there so the next editable default flag in settings has clear guidance.",
0 commit comments