claude-queue 1.2.2 → 1.3.0

package/dist/mcp/index.js

@@ -36,6 +36,17 @@ async function httpPatch(url, body) {
   }
   return response.json();
 }
+async function httpPut(url, body) {
+  const response = await fetch(`${KANBAN_URL}${url}`, {
+    method: "PUT",
+    headers: { "Content-Type": "application/json" },
+    body: JSON.stringify(body)
+  });
+  if (!response.ok) {
+    throw new Error(`HTTP ${response.status}: ${await response.text()}`);
+  }
+  return response.json();
+}
 
 // src/handlers/watch.ts
 async function handleWatch(args) {
@@ -374,6 +385,21 @@ Run one of the commands above to start working on that project's queue.`
   };
 }
 
+// src/handlers/project-prompt.ts
+async function handleSetProjectPrompt(args) {
+  const projectId = args?.projectId;
+  const prompt = args?.prompt;
+  await httpPut(`/api/prompts/project/${projectId}`, { content: prompt });
+  return {
+    content: [
+      {
+        type: "text",
+        text: `Project prompt updated for ${projectId}.`
+      }
+    ]
+  };
+}
+
 // src/index.ts
 var server = new McpServer({
   name: "claude-queue",
@@ -531,6 +557,19 @@ server.registerTool(
     return await handleListProjects();
   }
 );
+server.registerTool(
+  "queue_set_project_prompt",
+  {
+    description: "Set a brief project prompt (1-2 sentences) that provides context for all tasks. Used during planning to capture the project's purpose.",
+    inputSchema: {
+      projectId: z.string().describe("Project ID (e.g., kbn-a3x9)"),
+      prompt: z.string().max(300).describe("Brief project context (1-2 sentences, max 300 chars)")
+    }
+  },
+  async (args) => {
+    return await handleSetProjectPrompt(args);
+  }
+);
 async function main() {
   const transport = new StdioServerTransport();
   await server.connect(transport);

package/dist/skills/queue/SKILL.md

@@ -52,8 +52,12 @@ When invoked with `/queue plan <project-id>`:
 5. **Propose the plan**: Present a comprehensive plan document capturing everything discussed. Ask if it captures their intent correctly.
 6. **Refine until approved**: If the user wants changes, refine the plan. Repeat until they're happy.
 7. **Create/update CLAUDE.md**: Once approved, write the plan to CLAUDE.md in the project directory. This provides context for all future sessions.
-8. **Break into tasks**: Derive task titles and detailed descriptions from the plan
-9. **Ready to start?**: Ask "Ready to start? (or should I just add these to backlog for later?)"
+8. **Set project prompt**: Call `queue_set_project_prompt` with a brief 1-2 sentence summary of what the project is about
+9. **Break into tasks**: Create focused, actionable tasks:
+   - Avoid overly broad tasks - each should be completable in a single session
+   - Include enough context in descriptions so the task can be understood without CLAUDE.md
+   - Mention relevant files or components when helpful
+10. **Ready to start?**: Ask "Ready to start? (or should I just add these to backlog for later?)"
    - If user wants to start: Create tasks in "ready", then proceed to **Work Mode** and begin the main loop
    - If user wants backlog: Create tasks in "backlog", inform them they can start later by running `/queue <project-id>`
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-queue",
-  "version": "1.2.2",
+  "version": "1.3.0",
   "description": "A local kanban board for managing Claude Code projects",
   "type": "module",
   "bin": {