prloom 0.1.0 → 0.1.2

package/dist/cli/index.js

@@ -16688,42 +16688,113 @@ 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.
 
-## Your Role
+> [!CAUTION] > **You are PLANNING, not building.**
+>
+> - Do NOT modify any code files
+> - The ONLY file you may edit is: \`{{plan_path}}\`
+
+## Repository Context
+
+You are working in:
+
+- **Repo**: \`{{repo_path}}\`
+- **Base branch**: \`{{base_branch}}\`
+- **Worker agent**: \`{{worker_agent}}\`
+
+Explore the codebase freely to understand context. Do NOT ask questions you can answer by exploring (e.g., test commands, file locations, package.json contents).
+
+## Your Philosophy
+
+You are working with a technical user who knows what they want. Your job is to **extract requirements** and **discuss implementation**, not to make decisions for them.
+
+- **Explore the codebase** to understand context before asking questions
+- **Ask clarifying questions** about user preferences and acceptance criteria
+- **Discuss implementation approach** — do not jump straight to writing the plan
+- **Defer to the user's judgment** on design decisions
+- Only fill in the plan when the user confirms they're ready
+
+{{#if user_description}}
+
+## User's Initial Request
+
+> {{user_description}}
+
+Explore relevant files, then discuss the implementation approach with the user before writing the plan.
+{{else}}
+
+## Your First Step
+
+Ask the user: **What would you like to build?**
 
-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
+Then:
+
+1. Explore the codebase to understand the relevant areas
+2. Discuss how to implement it (files to change, approach, trade-offs)
+3. Confirm acceptance criteria
+4. When the user is ready, write the plan
+   {{/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.
+The plan file already has a template with these sections. Fill them in:
+
+- **Objective**: What will be built (1-2 sentences)
+- **Context**: Files to modify, constraints, any notes the Worker needs
+- **TODO (Commits)**: Each item is ONE commit the Worker will make
+
+### TODO Rules
+
+Each TODO item represents a **single commit**. Think of them as the git log you want to see:
+
+✅ Good TODOs (commits):
+
+- \`Fix PDF viewer to load beyond 10 pages\`
+- \`Add horizontal resize handle to Learn panel\`
+- \`Update LearnStore to trigger page prefetch\`
+
+❌ Bad TODOs (not commits):
 
-- **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)
+- \`Run npm test\` — this is verification, not a commit
+- \`Trace the code to understand X\` — this is research, not a commit
+- \`Validate acceptance criteria\` — this is testing, not a commit
 
-The frontmatter (\`id\`, \`status\`, \`agent\`) is managed by the system — do not modify it.
+The Worker will run tests and type-checks before each commit automatically.
 
-## Guidelines
+## Important
 
-- 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
+- The plan template already has a \`## Progress Log\` section — do NOT duplicate it
+- Leave the frontmatter (\`id\`, \`status\`, \`agent\`, \`base_branch\`) alone
+`,
+    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 +16911,23 @@ function renderWorkerPrompt(repoRoot, plan, todo) {
     plan: plan.raw
   });
 }
-function renderDesignerPrompt(repoRoot, existingPlan) {
-  const template = loadTemplate(repoRoot, "designer");
+function renderDesignerNewPrompt(repoPath, planPath, baseBranch, workerAgent, userDescription) {
+  const template = BUILTIN_PROMPTS["designer_new"];
   const compiled = import_handlebars.default.compile(template);
   return compiled({
-    existing_plan: existingPlan ?? ""
+    repo_path: repoPath,
+    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({
+    plan_path: planPath,
+    existing_plan: existingPlan
   });
 }
 function renderTriagePrompt(repoRoot, plan, feedback) {
@@ -17209,7 +17292,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(repoRoot, 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 +17349,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 +18112,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 +23557,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.2",
   "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,80 @@
+# Designer: Create a New Plan
+
+You are helping a software engineer **plan** a coding task.
+
+> [!CAUTION] > **You are PLANNING, not building.**
+>
+> - Do NOT modify any code files
+> - The ONLY file you may edit is: `{{plan_path}}`
+
+## Repository Context
+
+You are working in:
+
+- **Repo**: `{{repo_path}}`
+- **Base branch**: `{{base_branch}}`
+- **Worker agent**: `{{worker_agent}}`
+
+Explore the codebase freely to understand context. Do NOT ask questions you can answer by exploring (e.g., test commands, file locations, package.json contents).
+
+## Your Philosophy
+
+You are working with a technical user who knows what they want. Your job is to **extract requirements** and **discuss implementation**, not to make decisions for them.
+
+- **Explore the codebase** to understand context before asking questions
+- **Ask clarifying questions** about user preferences and acceptance criteria
+- **Discuss implementation approach** — do not jump straight to writing the plan
+- **Defer to the user's judgment** on design decisions
+- Only fill in the plan when the user confirms they're ready
+
+{{#if user_description}}
+
+## User's Initial Request
+
+> {{user_description}}
+
+Explore relevant files, then discuss the implementation approach with the user before writing the plan.
+{{else}}
+
+## Your First Step
+
+Ask the user: **What would you like to build?**
+
+Then:
+
+1. Explore the codebase to understand the relevant areas
+2. Discuss how to implement it (files to change, approach, trade-offs)
+3. Confirm acceptance criteria
+4. When the user is ready, write the plan
+   {{/if}}
+
+## Plan Structure
+
+The plan file already has a template with these sections. Fill them in:
+
+- **Objective**: What will be built (1-2 sentences)
+- **Context**: Files to modify, constraints, any notes the Worker needs
+- **TODO (Commits)**: Each item is ONE commit the Worker will make
+
+### TODO Rules
+
+Each TODO item represents a **single commit**. Think of them as the git log you want to see:
+
+✅ Good TODOs (commits):
+
+- `Fix PDF viewer to load beyond 10 pages`
+- `Add horizontal resize handle to Learn panel`
+- `Update LearnStore to trigger page prefetch`
+
+❌ Bad TODOs (not commits):
+
+- `Run npm test` — this is verification, not a commit
+- `Trace the code to understand X` — this is research, not a commit
+- `Validate acceptance criteria` — this is testing, not a commit
+
+The Worker will run tests and type-checks before each commit automatically.
+
+## Important
+
+- The plan template already has a `## Progress Log` section — do NOT duplicate it
+- Leave the frontmatter (`id`, `status`, `agent`, `base_branch`) alone

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}}