lalph 0.1.13 → 0.1.15

package/dist/cli.mjs

@@ -133898,7 +133898,7 @@ const LinearIssueSource = effect(IssueSource, gen(function* () {
 			priority: issue.priority,
 			estimate: issue.estimate ?? null,
 			stateId: issue.stateId,
-			complete: state.type !== "unstarted",
+			complete: state.type === "completed",
 			blockedBy: blockedBy.map((i) => i.identifier),
 			githubPrNumber: null
 		});
@@ -140399,10 +140399,13 @@ ${JSON.stringify(PrdIssue.jsonSchema, null, 2)}
 \`\`\``;
 	const prompt = `# Instructions
 
+The following instructions should be done without interaction or asking for
+permission.
+
 1. Decide which single task to work on next from the prd.json file. This should
    be the task YOU decide as the most important to work on next, not just the
    first task in the list.
-   - If a task is already completed or in review, skip it.
+   - Only start tasks that are in a "todo" state (i.e., not started yet).
    - If the \`blockedBy\` field is not empty, skip the task.
 2. **Before doing anything else**, mark the task as "in progress" by updating its
    \`stateId\` in the prd.json file.
@@ -140412,11 +140415,13 @@ ${JSON.stringify(PrdIssue.jsonSchema, null, 2)}
    - If there is an existing PR, checkout the branch for that PR.
    - If there is an existing PR, check if there are any new comments or requested
      changes, and address them as part of the task.
+   - If creating a new branch, don't checkout any main branches first, use the current
+     HEAD as the base.
    - New branches should be named using the format \`{task id}/description\`.
    - When checking for PR reviews, make sure to check the "reviews" field and read ALL unresolved comments.
 4. Research the task. If it seems like too many steps are needed to complete the task,
    break it down into smaller tasks and add them to the prd.json file, marking the
-   original task as "blocked" or "closed" by updating its \`stateId\`.
+   original task as "closed" by updating its \`stateId\`.
    Otherwise, implement the task.
 5. Run any checks / feedback loops, such as type checks, unit tests, or linting.
 6. Create or update the pull request with your progress.
@@ -140438,8 +140443,7 @@ important to work on next.
 
 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.json
-file. Then, mark the original task as "blocked" or "deferred" by updating its
-\`stateId\`.
+file. Then, mark the original task as "closed" by updating its \`stateId\`.
 
 Each task should be small and specific.
 Instead of creating tasks like "Refactor the authentication system", create

package/package.json

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

package/src/Linear.ts

@@ -180,7 +180,7 @@ export const LinearIssueSource = Layer.effect(
               priority: issue.priority,
               estimate: issue.estimate ?? null,
               stateId: issue.stateId!,
-              complete: state.type !== "unstarted",
+              complete: state.type === "completed",
               blockedBy: blockedBy.map((i) => i.identifier),
               githubPrNumber: null,
             })

package/src/PromptGen.ts

@@ -40,10 +40,13 @@ ${JSON.stringify(PrdIssue.jsonSchema, null, 2)}
 
       const prompt = `# Instructions
 
+The following instructions should be done without interaction or asking for
+permission.
+
 1. Decide which single task to work on next from the prd.json file. This should
    be the task YOU decide as the most important to work on next, not just the
    first task in the list.
-   - If a task is already completed or in review, skip it.
+   - Only start tasks that are in a "todo" state (i.e., not started yet).
    - If the \`blockedBy\` field is not empty, skip the task.
 2. **Before doing anything else**, mark the task as "in progress" by updating its
    \`stateId\` in the prd.json file.
@@ -53,11 +56,13 @@ ${JSON.stringify(PrdIssue.jsonSchema, null, 2)}
    - If there is an existing PR, checkout the branch for that PR.
    - If there is an existing PR, check if there are any new comments or requested
      changes, and address them as part of the task.
+   - If creating a new branch, don't checkout any main branches first, use the current
+     HEAD as the base.
    - New branches should be named using the format \`{task id}/description\`.
    - When checking for PR reviews, make sure to check the "reviews" field and read ALL unresolved comments.
 4. Research the task. If it seems like too many steps are needed to complete the task,
    break it down into smaller tasks and add them to the prd.json file, marking the
-   original task as "blocked" or "closed" by updating its \`stateId\`.
+   original task as "closed" by updating its \`stateId\`.
    Otherwise, implement the task.
 5. Run any checks / feedback loops, such as type checks, unit tests, or linting.
 6. Create or update the pull request with your progress.
@@ -79,8 +84,7 @@ important to work on next.
 
 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.json
-file. Then, mark the original task as "blocked" or "deferred" by updating its
-\`stateId\`.
+file. Then, mark the original task as "closed" by updating its \`stateId\`.
 
 Each task should be small and specific.
 Instead of creating tasks like "Refactor the authentication system", create