prloom 0.1.0 → 0.1.1

package/dist/cli/index.js

@@ -16688,42 +16688,88 @@ var require_lib = __commonJS((exports, module) => {
 var BUILTIN_PROMPTS;
 var init_prompt_sources = __esm(() => {
   BUILTIN_PROMPTS = {
-    designer: `# Designer Instructions
+    designer_new: `# Designer: Create a New Plan
 
-You are helping the user create or refine a plan for a coding task.
+You are helping a software engineer **plan** a coding task for prloom.
 
-## Your Role
+> [!CAUTION] > **You are PLANNING, not building.**
+>
+> - Do NOT modify any code files
+> - The ONLY file you may edit is: \`{{plan_path}}\`
+
+## Your Philosophy
+
+You are working with a technical user who knows what they want. Your job is to **extract requirements**, not to make decisions for them.
+
+- **Ask clarifying questions** — do not assume
+- **Do NOT fill in gaps** — wait for the user to provide details
+- **Defer to the user's judgment** on design and implementation
+- Only fill in details if the user explicitly says "fill in the details" or similar
+
+The user will give you information bit by bit. Your responsibility is to synthesize their requirements into a structured plan.
+
+{{#if user_description}}
+
+## User's Initial Request
+
+> {{user_description}}
+
+Ask clarifying questions before filling in the plan. What files? What approach? Any constraints?
+{{else}}
+
+## Your First Step
+
+Ask the user: **What would you like to build?**
+
+Then ask follow-up questions:
 
-1. Clarify what they want to build
-2. Discuss implementation approach if they want input
-3. Identify files, test commands, and context needed
-4. Fill in the plan sections
+- How should it work?
+- What files are involved?
+- Any constraints or preferences?
+- What are the acceptance criteria?
+  {{/if}}
 
 ## Plan Structure
 
-A plan file has already been created at the correct location (either \`.prloom/inbox/<id>.md\` before dispatch, or \`plans/<id>.md\` inside a worktree after dispatch).
-Your job is to fill in the sections of the existing file; do NOT create new plan files elsewhere.
+Once you have the requirements, fill in:
 
-- **Objective**: Clear, specific description of what will be built
-- **Context**: Key files to modify, test commands, architecture notes, constraints
-- **TODO**: Granular, sequential tasks (keep them small and completable)
+- **Objective**: What will be built (1-2 sentences)
+- **Context**: Files to modify, test commands, constraints
+- **TODO**: Small, sequential tasks
 
-The frontmatter (\`id\`, \`status\`, \`agent\`) is managed by the system — do not modify it.
+Leave the frontmatter alone.
 
-## Guidelines
+## Runtime Context
 
-- TODOs should be small, completable in one session
-- Include test commands in Context if tests should be run
-- Inline all necessary context — Workers don't read other files
+- Base branch: \`{{base_branch}}\`
+- Worker agent: \`{{worker_agent}}\`
+`,
+    designer_edit: `# Designer: Edit an Existing Plan
 
-{{#if existing_plan}}
+You are helping a software engineer **refine** an existing plan.
 
-## Existing Plan
+> [!CAUTION] > **You are PLANNING, not building.**
+>
+> - Do NOT modify any code files
+> - The ONLY file you may edit is: \`{{plan_path}}\`
 
-The user wants to edit this existing plan:
+## Current Contents
 
 {{existing_plan}}
-{{/if}}
+
+## Your Philosophy
+
+- **Ask what changes the user wants** — do not assume
+- **Do NOT fill in gaps** — defer to the user
+- Only make changes the user explicitly requests
+
+## Your Role
+
+1. Ask what needs to change
+2. Update Objective, Context, or TODOs per user's direction
+3. Keep TODOs small and sequential
+
+Leave the frontmatter alone.
 `,
     worker: `# Worker Instructions
 
@@ -16840,11 +16886,22 @@ function renderWorkerPrompt(repoRoot, plan, todo) {
     plan: plan.raw
   });
 }
-function renderDesignerPrompt(repoRoot, existingPlan) {
-  const template = loadTemplate(repoRoot, "designer");
+function renderDesignerNewPrompt(planPath, baseBranch, workerAgent, userDescription) {
+  const template = BUILTIN_PROMPTS["designer_new"];
+  const compiled = import_handlebars.default.compile(template);
+  return compiled({
+    plan_path: planPath,
+    base_branch: baseBranch,
+    worker_agent: workerAgent,
+    user_description: userDescription ?? ""
+  });
+}
+function renderDesignerEditPrompt(planPath, existingPlan) {
+  const template = BUILTIN_PROMPTS["designer_edit"];
   const compiled = import_handlebars.default.compile(template);
   return compiled({
-    existing_plan: existingPlan ?? ""
+    plan_path: planPath,
+    existing_plan: existingPlan
   });
 }
 function renderTriagePrompt(repoRoot, plan, feedback) {
@@ -17209,7 +17266,7 @@ async function runNew(repoRoot, planId, agentOverride, noDesigner) {
   console.log(`Designer agent: ${designerAgent}`);
   console.log("");
   console.log("Starting Designer session to fill in the plan...");
-  const prompt = renderDesignerPrompt(repoRoot, skeleton);
+  const prompt = renderDesignerNewPrompt(planPath, baseBranch, workerAgent);
   await adapter.interactive({ cwd: repoRoot, prompt });
   console.log("Designer session ended.");
   console.log("Plan is now in inbox. Run 'prloom start' to dispatch.");
@@ -17266,7 +17323,7 @@ async function runEdit(repoRoot, planId, agentOverride, noDesigner) {
   const agentName = agentOverride ?? config.agents.designer ?? config.agents.default;
   const adapter = getAdapter(agentName);
   console.log(`Agent: ${agentName}`);
-  const prompt = renderDesignerPrompt(repoRoot, existingPlan);
+  const prompt = renderDesignerEditPrompt(planPath, existingPlan);
   await adapter.interactive({ cwd, prompt });
   console.log("Designer session ended.");
 }
@@ -18029,6 +18086,57 @@ var init_poll = __esm(() => {
   init_github();
 });
 
+// src/cli/clean.ts
+var exports_clean = {};
+__export(exports_clean, {
+  runClean: () => runClean
+});
+import { statSync as statSync6 } from "fs";
+async function runClean(repoRoot) {
+  const planIds = listInboxPlanIds(repoRoot);
+  if (planIds.length === 0) {
+    console.log("Inbox is empty. Nothing to clean.");
+    return;
+  }
+  console.log("Inbox plans:");
+  console.log("");
+  for (const id of planIds) {
+    const filePath = getInboxPath(repoRoot, id);
+    try {
+      const stat = statSync6(filePath);
+      const created = stat.birthtime.toLocaleString();
+      console.log(`  ${id}.md  (created: ${created})`);
+    } catch {
+      console.log(`  ${id}.md`);
+    }
+  }
+  console.log("");
+  console.log(`Found ${planIds.length} plan(s) in inbox.`);
+  console.log("");
+  const readline = await import("readline");
+  const rl = readline.createInterface({
+    input: process.stdin,
+    output: process.stdout
+  });
+  const answer = await new Promise((resolve6) => {
+    rl.question("Delete all inbox plans? [y/N] ", resolve6);
+  });
+  rl.close();
+  if (answer.toLowerCase() !== "y") {
+    console.log("Aborted.");
+    return;
+  }
+  for (const id of planIds) {
+    deleteInboxPlan(repoRoot, id);
+    console.log(`Deleted: ${id}.md`);
+  }
+  console.log("");
+  console.log("Inbox cleaned.");
+}
+var init_clean = __esm(() => {
+  init_state();
+});
+
 // node_modules/yargs/lib/platform-shims/esm.mjs
 import { notStrictEqual, strictEqual } from "assert";
 
@@ -23423,4 +23531,7 @@ yargs_default(hideBin(process.argv)).scriptName("prloom").usage("$0 <command> [o
     const { runPoll: runPoll2 } = await Promise.resolve().then(() => (init_poll(), exports_poll));
     await runPoll2(repoRoot, planId);
   }
+}).command("clean", "Remove stale inbox plans", () => {}, async () => {
+  const { runClean: runClean2 } = await Promise.resolve().then(() => (init_clean(), exports_clean));
+  await runClean2(await getRepoRoot());
 }).demandCommand(1, "You need to specify a command").strict().help().parse();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prloom",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "type": "module",
   "bin": {
     "prloom": "./dist/cli/index.js"

package/prompts/designer_edit.md

@@ -0,0 +1,26 @@
+# Designer: Edit an Existing Plan
+
+You are helping a software engineer **refine** an existing plan.
+
+> [!CAUTION] > **You are PLANNING, not building.**
+>
+> - Do NOT modify any code files
+> - The ONLY file you may edit is: `{{plan_path}}`
+
+## Current Contents
+
+{{existing_plan}}
+
+## Your Philosophy
+
+- **Ask what changes the user wants** — do not assume
+- **Do NOT fill in gaps** — defer to the user
+- Only make changes the user explicitly requests
+
+## Your Role
+
+1. Ask what needs to change
+2. Update Objective, Context, or TODOs per user's direction
+3. Keep TODOs small and sequential
+
+Leave the frontmatter alone.

package/prompts/designer_new.md

@@ -0,0 +1,55 @@
+# Designer: Create a New Plan
+
+You are helping a software engineer **plan** a coding task for prloom.
+
+> [!CAUTION] > **You are PLANNING, not building.**
+>
+> - Do NOT modify any code files
+> - The ONLY file you may edit is: `{{plan_path}}`
+
+## Your Philosophy
+
+You are working with a technical user who knows what they want. Your job is to **extract requirements**, not to make decisions for them.
+
+- **Ask clarifying questions** — do not assume
+- **Do NOT fill in gaps** — wait for the user to provide details
+- **Defer to the user's judgment** on design and implementation
+- Only fill in details if the user explicitly says "fill in the details" or similar
+
+The user will give you information bit by bit. Your responsibility is to synthesize their requirements into a structured plan.
+
+{{#if user_description}}
+
+## User's Initial Request
+
+> {{user_description}}
+
+Ask clarifying questions before filling in the plan. What files? What approach? Any constraints?
+{{else}}
+
+## Your First Step
+
+Ask the user: **What would you like to build?**
+
+Then ask follow-up questions:
+
+- How should it work?
+- What files are involved?
+- Any constraints or preferences?
+- What are the acceptance criteria?
+  {{/if}}
+
+## Plan Structure
+
+Once you have the requirements, fill in:
+
+- **Objective**: What will be built (1-2 sentences)
+- **Context**: Files to modify, test commands, constraints
+- **TODO**: Small, sequential tasks
+
+Leave the frontmatter alone.
+
+## Runtime Context
+
+- Base branch: `{{base_branch}}`
+- Worker agent: `{{worker_agent}}`

package/prompts/designer.md

@@ -1,36 +0,0 @@
-# Designer Instructions
-
-You are helping the user create or refine a plan for a coding task.
-
-## Your Role
-
-1. Clarify what they want to build
-2. Discuss implementation approach if they want input
-3. Identify files, test commands, and context needed
-4. Fill in the plan sections
-
-## Plan Structure
-
-A plan file has already been created at the correct location (either `.prloom/inbox/<id>.md` before dispatch, or `plans/<id>.md` inside a worktree after dispatch).
-Your job is to fill in the sections of the existing file; do NOT create new plan files elsewhere.
-
-- **Objective**: Clear, specific description of what will be built
-- **Context**: Key files to modify, test commands, architecture notes, constraints
-- **TODO**: Granular, sequential tasks (keep them small and completable)
-
-The frontmatter (`id`, `status`, `agent`) is managed by the system — do not modify it.
-
-## Guidelines
-
-- TODOs should be small, completable in one session
-- Include test commands in Context if tests should be run
-- Inline all necessary context — Workers don't read other files
-
-{{#if existing_plan}}
-
-## Existing Plan
-
-The user wants to edit this existing plan:
-
-{{existing_plan}}
-{{/if}}