@selesai/code 0.5.18 → 0.5.19

package/dist/extensions/workflow/modes/prototype.ts

@@ -33,27 +33,20 @@ const prompts: Partial<Record<Phase, (ctx: PromptContext) => string>> = {
 User request:
 ${userPrompt}
 
-Use the question tool to grill the user until requirements are unambiguous. Ask focused clarifying questions ONE question tool call at a time. Adapt each follow-up to what the user reveals. Dig into scope, constraints, success criteria, and edge cases. Use your judgement — no fixed checklist.
+Map requirements as a design tree: every decision branches into dependent decisions. Work the tree in rounds. The frontier contains every decision whose prerequisites are settled; do not ask questions that depend on answers still open in the current round.
+
+For each round, use one question tool call to ask the ENTIRE frontier. Number every question, give a recommended answer, and wait for the user's answers before the next round. Recompute the frontier after every response. Cover scope, constraints, success criteria, and edge cases; leave no branch silently assumed.
+
+Facts are yours to find, never the user's. When a frontier question needs a fact from the workspace or available tools, dispatch a sub-agent to investigate rather than asking the user. Do not block on it: ask other frontier decisions now; defer only decisions that depend on the pending finding.
 
 For each question tool call:
-- Provide a concise question.
+- State all numbered frontier questions concisely, including a recommendation for each.
 - Pass a short context summary when it depends on prior findings.
-- Prefer options when choices are known. Give each option a clear label and a brief description.
-- Always set allowFreeform=true so the user can type a custom answer.
+- Prefer options when one shared option set fits the whole round. Give each option a clear label and brief description.
+- Always set allowFreeform=true so the user can answer each numbered decision or provide a custom answer.
 - Keep allowMultiple=false unless multiple selections genuinely apply.
 
-Example:
-  question({
-    question: "What should the output format be?",
-    context: "The user wants a report generator. We need to pick the default export format.",
-    options: [
-      { label: "Markdown", description: "Simple, version-control friendly" },
-      { label: "PDF", description: "Polished, shareable document" },
-    ],
-    allowFreeform: true,
-  })
-
-When shared understanding is reached, do NOT write the file yet. Show a concise requirements summary draft and ask exactly: "Approve writing this requirements summary to ${artifactDir}/requirements.md?" Allow "keep grilling" or added details.
+Only when the frontier is empty, show a concise requirements summary draft and ask exactly: "Approve writing this requirements summary to ${artifactDir}/requirements.md?" This approval confirms shared understanding. Allow "keep grilling" or added details; do not write or otherwise act on the requirements before explicit approval.
 
 Artifact target: ${artifactDir}/requirements.md
 - Name that exact full path in the approval question.

package/dist/extensions/workflow/modes/quick.ts

@@ -11,8 +11,8 @@ import {
   reviewValidator,
 } from "../validators.ts";
 
-// ponytail: quick workflow — same tool-driven loop as prototype, but shorter:
-// grill (max 4 questions) → plan → reuse → handoff → loop → audit.
+// ponytail: quick workflow — same tool-driven loop as prototype, without research:
+// grill → plan → reuse → handoff → loop → audit.
 // No research phase. skipRules + closeArtifacts wired by the adapter.
 
 const phases: Phase[] = [
@@ -31,27 +31,20 @@ const prompts: Partial<Record<Phase, (ctx: PromptContext) => string>> = {
 User request:
 ${userPrompt}
 
-Use the question tool to grill the user. Ask AT MOST 4 focused clarifying questions — ONE question tool call at a time. Adapt each follow-up to prior answers. Dig into scope, constraints, success criteria, and edge cases.
+Map requirements as a design tree: every decision branches into dependent decisions. Work the tree in rounds. The frontier contains every decision whose prerequisites are settled; do not ask questions that depend on answers still open in the current round.
+
+For each round, use one question tool call to ask the ENTIRE frontier. Number every question, give a recommended answer, and wait for the user's answers before the next round. Recompute the frontier after every response. Cover scope, constraints, success criteria, and edge cases; leave no branch silently assumed.
+
+Facts are yours to find, never the user's. When a frontier question needs a fact from the workspace or available tools, dispatch a sub-agent to investigate rather than asking the user. Do not block on it: ask other frontier decisions now; defer only decisions that depend on the pending finding.
 
 For each question tool call:
-- Provide a concise question.
+- State all numbered frontier questions concisely, including a recommendation for each.
 - Pass a short context summary when it depends on prior findings.
-- Prefer options when choices are known. Give each option a clear label and a brief description.
-- Always set allowFreeform=true so the user can type a custom answer.
+- Prefer options when one shared option set fits the whole round. Give each option a clear label and brief description.
+- Always set allowFreeform=true so the user can answer each numbered decision or provide a custom answer.
 - Keep allowMultiple=false unless multiple selections genuinely apply.
 
-Example:
-  question({
-    question: "What should the output format be?",
-    context: "The user wants a report generator. We need to pick the default export format.",
-    options: [
-      { label: "Markdown", description: "Simple, version-control friendly" },
-      { label: "PDF", description: "Polished, shareable document" },
-    ],
-    allowFreeform: true,
-  })
-
-When you have enough clarity OR up to 10 questions max (less is better) have been asked, stop grilling. Show a concise requirements summary, then ask exactly: "Approve writing this requirements summary to ${artifactDir}/requirements.md?"
+Only when the frontier is empty, show a concise requirements summary draft and ask exactly: "Approve writing this requirements summary to ${artifactDir}/requirements.md?" This approval confirms shared understanding. Allow "keep grilling" or added details; do not write or otherwise act on the requirements before explicit approval.
 
 Artifact target: ${artifactDir}/requirements.md
 - Name that exact full path in the approval question.

package/dist/skills/batch-grill-me/SKILL.md

@@ -0,0 +1,15 @@
+---
+name: batch-grill-me
+description: A relentless interview that asks every frontier question at once, round by round.
+disable-model-invocation: true
+---
+
+Interview the user relentlessly until you reach a shared understanding. Map this as a **design tree**: every decision branches into the decisions that hang off it.
+
+Work the tree in **rounds**. The **frontier** is every decision whose prerequisites are already settled — the questions you can ask *now* without guessing at answers you haven't heard yet. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round.
+
+Each round the user answers reshapes the tree — settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a *later* round, not this one.
+
+Finding *facts* is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it — don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report — ask the rest of the frontier now. The *decisions* are the user's — put each to them and wait.
+
+The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Do not act on it until the user confirms you have reached a shared understanding.

package/dist/skills/selesai-handoff/SKILL.md

@@ -0,0 +1,20 @@
+---
+name: selesai-handoff
+description: Hand the current conversation off to a fresh background agent that picks up the work immediately.
+argument-hint: "What will the next session be used for?"
+disable-model-invocation: true
+---
+
+Write a handoff summary of the current conversation so a fresh agent can continue the work. Instead of saving it, launch a background agent seeded with the summary as its prompt: `selesai --name "<descriptive name>" -p "<handoff summary>"`. It starts in the current working directory and returns immediately; the user manages it with `selesai agents`.
+
+Always pass `-n`/`--name` with a descriptive name (e.g. `--name "Fix login bug"`) — it sets the display name shown in the job list, session picker, and terminal title.
+
+You might want to use something like `nohup` or `Start-Process` or `start /b` or etc. before the selesai command to spawn background command.
+
+Include a "suggested skills" section in the summary, which suggests skills that the agent should invoke.
+
+Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
+
+Redact any sensitive information, such as API keys, passwords, or personally identifiable information — the summary becomes the agent's prompt.
+
+If the user passed arguments, treat them as a description of what the next session will focus on and tailor the summary accordingly.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@selesai/code",
-	"version": "0.5.18",
+	"version": "0.5.19",
 	"description": "Maintained, extension-first Pi coding agent with built-in workflows, subagents, web research, questions, skills, and an enhanced terminal UI.",
 	"type": "module",
 	"repository": {