lalph 0.1.27 → 0.1.28

package/dist/cli.mjs

@@ -140150,7 +140150,7 @@ If at any point you decide that a task is too large or complex to complete in a
 single iteration, break it down into smaller tasks and add them to the prd.yml
 file. Then, mark the original task as "done" by updating its \`state\`.
 
-Each task should be small and specific.
+Each task should be an atomic, committable piece of work.
 Instead of creating tasks like "Refactor the authentication system", create
 smaller tasks like "Implement OAuth2 login endpoint", "Add JWT token refresh mechanism", etc.
 
@@ -140197,20 +140197,22 @@ ${prdNotes}`;
 	const promptTimeout = (options) => `# Instructions
 
 Your earlier attempt to complete the task with id \`${options.taskId}\` took too
-long and has timed out.
+long and has timed out. You can find the task details in the prd.yml file.
 
 The following instructions should be done without interaction or asking for
 permission.
 
-1. Research and break down the task into smaller tasks and add them to the prd.yml file.
-2. Mark the original task as "done" by updating its \`state\` in the prd.yml file.
-3. Each new task should have an id of \`null\`, a title, and a concise description that
+1. Investigate why you think the task took too long. Research the codebase
+   further if needed.
+2. Break down the task into smaller tasks and add them to the prd.yml file.
+3. Mark the original task as "done" by updating its \`state\` in the prd.yml file.
+4. Each new task should have an id of \`null\`, a title, and a concise description that
    includes a short summary of the task and a brief list of steps to complete it.
    - The tasks should start in the "todo" state.
-   - Each task should be small and specific.
+   - Each task should be an atomic, committable piece of work.
      Instead of creating tasks like "Refactor the authentication system", create
      smaller tasks like "Implement OAuth2 login endpoint", "Add JWT token refresh mechanism", etc.
-4. Setup task dependencies using the \`blockedBy\` field as needed. You will need
+5. Setup task dependencies using the \`blockedBy\` field as needed. You will need
    to wait 5 seconds after adding tasks to the prd.yml file to allow the system
    to assign ids to the new tasks before you can setup dependencies.
 
@@ -140230,7 +140232,7 @@ ${prdNotes}`;
 2. Each task should have a id of \`null\`, a title, and a concise description that
    includes a short summary of the task and a brief list of steps to complete it.
    - The tasks should start in the "todo" state.
-   - Each task should be small and specific.
+   - Each task should be an atomic, committable piece of work.
      Instead of creating tasks like "Refactor the authentication system", create
      smaller tasks like "Implement OAuth2 login endpoint", "Add JWT token refresh mechanism", etc.
 3. Add the new tasks to the prd.yml file.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "lalph",
   "type": "module",
-  "version": "0.1.27",
+  "version": "0.1.28",
   "publishConfig": {
     "access": "public"
   },

package/src/PromptGen.ts

@@ -73,7 +73,7 @@ If at any point you decide that a task is too large or complex to complete in a
 single iteration, break it down into smaller tasks and add them to the prd.yml
 file. Then, mark the original task as "done" by updating its \`state\`.
 
-Each task should be small and specific.
+Each task should be an atomic, committable piece of work.
 Instead of creating tasks like "Refactor the authentication system", create
 smaller tasks like "Implement OAuth2 login endpoint", "Add JWT token refresh mechanism", etc.
 
@@ -127,20 +127,22 @@ ${prdNotes}`
       }) => `# Instructions
 
 Your earlier attempt to complete the task with id \`${options.taskId}\` took too
-long and has timed out.
+long and has timed out. You can find the task details in the prd.yml file.
 
 The following instructions should be done without interaction or asking for
 permission.
 
-1. Research and break down the task into smaller tasks and add them to the prd.yml file.
-2. Mark the original task as "done" by updating its \`state\` in the prd.yml file.
-3. Each new task should have an id of \`null\`, a title, and a concise description that
+1. Investigate why you think the task took too long. Research the codebase
+   further if needed.
+2. Break down the task into smaller tasks and add them to the prd.yml file.
+3. Mark the original task as "done" by updating its \`state\` in the prd.yml file.
+4. Each new task should have an id of \`null\`, a title, and a concise description that
    includes a short summary of the task and a brief list of steps to complete it.
    - The tasks should start in the "todo" state.
-   - Each task should be small and specific.
+   - Each task should be an atomic, committable piece of work.
      Instead of creating tasks like "Refactor the authentication system", create
      smaller tasks like "Implement OAuth2 login endpoint", "Add JWT token refresh mechanism", etc.
-4. Setup task dependencies using the \`blockedBy\` field as needed. You will need
+5. Setup task dependencies using the \`blockedBy\` field as needed. You will need
    to wait 5 seconds after adding tasks to the prd.yml file to allow the system
    to assign ids to the new tasks before you can setup dependencies.
 
@@ -157,7 +159,7 @@ ${prdNotes}`
 2. Each task should have a id of \`null\`, a title, and a concise description that
    includes a short summary of the task and a brief list of steps to complete it.
    - The tasks should start in the "todo" state.
-   - Each task should be small and specific.
+   - Each task should be an atomic, committable piece of work.
      Instead of creating tasks like "Refactor the authentication system", create
      smaller tasks like "Implement OAuth2 login endpoint", "Add JWT token refresh mechanism", etc.
 3. Add the new tasks to the prd.yml file.