lalph 0.1.38 → 0.1.40

package/dist/cli.mjs

@@ -44313,18 +44313,18 @@ const defaultFormatter = (options) => {
 		yellow: (text$3) => text$3,
 		magenta: (text$3) => text$3
 	};
-	const reset$1 = useColor ? "\x1B[0m" : "";
+	const reset$2 = useColor ? "\x1B[0m" : "";
 	const red$1 = useColor ? "\x1B[31m" : "";
 	const bold$1 = useColor ? "\x1B[1m" : "";
 	return {
 		formatHelpDoc: (doc) => formatHelpDocImpl(doc, colors$1),
 		formatCliError: (error$1) => error$1.message,
 		formatError: (error$1) => {
-			return `\n${bold$1}${red$1}ERROR${reset$1}\n  ${error$1.message}${reset$1}`;
+			return `\n${bold$1}${red$1}ERROR${reset$2}\n  ${error$1.message}${reset$2}`;
 		},
 		formatErrors: (errors) => {
 			if (errors.length === 0) return "";
-			if (errors.length === 1) return `\n${bold$1}${red$1}ERROR${reset$1}\n  ${errors[0].message}${reset$1}`;
+			if (errors.length === 1) return `\n${bold$1}${red$1}ERROR${reset$2}\n  ${errors[0].message}${reset$2}`;
 			const grouped = /* @__PURE__ */ new Map();
 			for (const error$1 of errors) {
 				const tag$1 = error$1._tag ?? "Error";
@@ -44333,8 +44333,8 @@ const defaultFormatter = (options) => {
 				grouped.set(tag$1, group);
 			}
 			const sections = [];
-			sections.push(`\n${bold$1}${red$1}ERRORS${reset$1}`);
-			for (const [, group] of grouped) for (const error$1 of group) sections.push(`  ${error$1.message}${reset$1}`);
+			sections.push(`\n${bold$1}${red$1}ERRORS${reset$2}`);
+			for (const [, group] of grouped) for (const error$1 of group) sections.push(`  ${error$1.message}${reset$2}`);
 			return sections.join("\n");
 		},
 		formatVersion: (name, version$1) => `${colors$1.bold(name)} ${colors$1.dim("v")}${colors$1.bold(version$1)}`
@@ -45917,7 +45917,7 @@ const ESC = "\x1B[";
 const BEL = "\x07";
 const SEP = ";";
 /** @internal */
-const reset = `${ESC}0m`;
+const reset$1 = `${ESC}0m`;
 /** @internal */
 const bold = `${ESC}1m`;
 /** @internal */
@@ -45973,7 +45973,7 @@ const cyanBright = `${ESC}96m`;
 /** @internal */
 const whiteBright = `${ESC}97m`;
 const annotate = (text$3, ...styles) => {
-	return `${styles.flat().join("")}${text$3}${reset}`;
+	return `${styles.flat().join("")}${text$3}${reset$1}`;
 };
 const combine = (...styles) => styles;
 /** @internal */
@@ -53173,7 +53173,7 @@ function make$12() {
 		pairs: 0,
 		size: 0
 	};
-	function reset$1(value) {
+	function reset$2(value) {
 		state.state = State$1.key;
 		state.headers = Object.create(null);
 		state.key = "";
@@ -53191,7 +53191,7 @@ function make$12() {
 		return newUint8Array;
 	}
 	function error$1(reason) {
-		return reset$1({
+		return reset$2({
 			_tag: "Failure",
 			reason,
 			headers: state.headers
@@ -53293,7 +53293,7 @@ function make$12() {
 							state.size--;
 							if (state.crlf !== 4 && state.pairs === constMaxPairs) return error$1("TooManyHeaders");
 							else if (state.crlf === 3) return error$1("InvalidHeaderValue");
-							else if (state.crlf === 4) return reset$1({
+							else if (state.crlf === 4) return reset$2({
 								_tag: "Headers",
 								headers: state.headers,
 								endPosition: start - endOffset
@@ -140379,6 +140379,9 @@ const getOrSelectIssueSource = gen(function* () {
 	if (isSome(issueSource)) return issueSources.find((s) => s.id === issueSource.value);
 	return yield* selectIssueSource;
 });
+const resetCurrentIssueSource = gen(function* () {
+	yield* (yield* getOrSelectIssueSource).reset;
+});
 var CurrentIssueSource = class CurrentIssueSource extends Service()("lalph/CurrentIssueSource") {
 	static layer = effectServices(gen(function* () {
 		const source = yield* getOrSelectIssueSource;
@@ -140414,6 +140417,8 @@ To add a new task, append a new item to the prd.yml file with the id set to
 When adding a new task, it will take about 5 seconds for the system to update the
 prd.yml file with a new id for the task.
 
+After adding a new task, you can setup dependencies using the \`blockedBy\` field
+
 ### Removing tasks
 
 To remove a task, simply delete the item from the prd.yml file.
@@ -140449,16 +140454,6 @@ The following instructions should be done without interaction or asking for perm
 }
 \`\`\`
 
-## Important: Task sizing
-
-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 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.
-
 ${prdNotes}`;
 	const prompt = (options) => `# Instructions
 
@@ -140466,6 +140461,8 @@ The following instructions should be done without interaction or asking for
 permission.
 
 1. Your job is to complete the task with id \`${options.taskId}\` from the prd.yml file.
+   Read the entire prd.yml file to understand the context of the task and any
+   key learnings from previous work.
 2. Check if there is an existing Github PR for the task, otherwise create a new
    branch for the task.${options.targetBranch ? ` The target branch for the PR should be \`${options.targetBranch}\`. If the target branch does not exist, create it first.` : ""}
    - If there is an existing PR, checkout the branch for that PR.
@@ -140477,15 +140474,6 @@ permission.
    - When checking for PR reviews, make sure to check the "reviews" field and read ALL unresolved comments.
      Also read the normal comments to see if there are any additional requests.
 4. Implement the task.
-   - This session will time out after a certain period, so make sure to record
-     key information that could speed up future work on the task in the task
-     description. Record the information **in the moment** as you discover it,
-     do not wait until the end of the task. Things to record include:
-     - Important discoveries about the codebase.
-     - Any challenges faced and how you overcame them.
-     - APIs / libraries discovered that were useful.
-     - Links to relevant documentation.
-     - Any other information that could help future work on 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.
    ${sourceMeta.githubPrInstructions}
@@ -140495,13 +140483,27 @@ permission.
      permission to push branches, create PRs or create git commits.
 7. Update the prd.yml file to reflect any changes in task states.
    - Update the prd.yml file after the GitHub PR has been created or updated.
-   - Add follow up tasks only if needed.
-   - Append to the \`description\` field with any notes or important discoveries.
+   - Rewrite the notes in the description to include only the key discoveries
+     and information that could speed up future work on other tasks.
    - If you believe the task is complete, update the \`state\` to "in-review".
 
-**Remember:** record key information that could speed up future work on the task in
-the task description **in the moment** as you discover it, do not wait until
-the end of the task.
+## Important: Adding new tasks
+
+**If at any point** you discover something that needs fixing, or another task
+that needs doing, immediately add it to the prd.yml file as a new task.
+
+## Important: Recording key information
+
+This session will time out after a certain period, so make sure to record
+key information that could speed up future work on the task in the description.
+Record the information **in the moment** as you discover it,
+do not wait until the end of the task. Things to record include:
+
+- Important discoveries about the codebase.
+- Any challenges faced and how you overcame them.
+  - If it took multiple attempts to get something working, record what worked.
+  - If you found a library api was renamed or moved, record the new name.
+- Any other information that could help future work on similar tasks.
 
 ## Handling blockers
 
@@ -140546,7 +140548,7 @@ ${prdNotes}`;
    - Make sure to research the codebase before creating the specification, to
      ensure it is relevant and feasible.
 2. Once you have saved the specification, your next job is to break down the
-   specification into smaller, manageable tasks.
+   specification into smaller, manageable tasks and add them to the prd.yml file.
    Each task should have a id of \`null\`, a title, and a concise description that
    includes a where to find the plan specification, a short summary of the task and a
    brief list of steps to complete it.
@@ -140554,13 +140556,12 @@ ${prdNotes}`;
    - 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.
-   - **Never** create a research task. You should do all the necessary research
-     before creating the specification and tasks. Instead of creating a task like
-     "Research endpoints to refactor", investigate then endpoints first then create
-     tasks like "Implement user profile endpoint", "Refactor authentication endpoint", etc.
-3. Add the new or updated tasks to the prd.yml file.
-4. Wait until the tasks are saved, then setup task dependencies using the \`blockedBy\` field.
-5. Start a subagent with a copy of this prompt, to review the plan and provide feedback or improvements.
+   - If you need to add a research task, mention in the description that it needs to:
+     - add a specification file in the \`${options.specsDirectory}\` directory.
+     - add follow up tasks in the prd.yml file based on the new specification. The tasks
+       should reference the specification file in their description.
+3. Wait until the tasks are saved, then setup task dependencies using the \`blockedBy\` field.
+4. Start a subagent with a copy of this prompt, to review the plan and provide feedback or improvements.
 
 **Important:** You are only creating or updating a plan, not implementing any tasks yet.
 
@@ -140943,7 +140944,14 @@ const createIssue = make$25("issue").pipe(withDescription("Create a new issue in
 const selectAgent = make$25("agent").pipe(withDescription("Select the CLI agent to use"), withHandler(() => selectCliAgent));
 const selectSource = make$25("source").pipe(withDescription("Select the issue source to use"), withHandler(() => selectIssueSource));
 const specsDirectory = directory("specs").pipe(withDescription$1("Directory to store plan specifications"), withAlias("s"), withDefault(".specs"));
-const planMode = make$25("plan", { specsDirectory }).pipe(withDescription("Iterate on an issue plan and create PRD tasks"), withHandler(plan), provide(CurrentIssueSource.layer));
+const reset = boolean("reset").pipe(withDescription$1("Reset the current issue source before planning"), withAlias("r"));
+const planMode = make$25("plan", {
+	specsDirectory,
+	reset
+}).pipe(withDescription("Iterate on an issue plan and create PRD tasks"), withHandler(fnUntraced(function* (options) {
+	if (options.reset) yield* resetCurrentIssueSource;
+	yield* plan(options).pipe(provide$1(CurrentIssueSource.layer));
+})));
 const iterations = integer("iterations").pipe(withDescription$1("Number of iterations to run, defaults to unlimited"), withAlias("i"), withDefault(Number.POSITIVE_INFINITY));
 const concurrency = integer("concurrency").pipe(withDescription$1("Number of concurrent agents, defaults to 1"), withAlias("c"), withDefault(1));
 const autoMerge = boolean("auto-merge").pipe(withAlias("a"), withDescription$1("Automatically merge eligible PRs"));

package/package.json

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

package/src/IssueSources.ts

@@ -48,6 +48,11 @@ const getOrSelectIssueSource = Effect.gen(function* () {
   return yield* selectIssueSource
 })
 
+export const resetCurrentIssueSource = Effect.gen(function* () {
+  const source = yield* getOrSelectIssueSource
+  yield* source.reset
+})
+
 export class CurrentIssueSource extends ServiceMap.Service<
   CurrentIssueSource,
   {

package/src/PromptGen.ts

@@ -31,6 +31,8 @@ To add a new task, append a new item to the prd.yml file with the id set to
 When adding a new task, it will take about 5 seconds for the system to update the
 prd.yml file with a new id for the task.
 
+After adding a new task, you can setup dependencies using the \`blockedBy\` field
+
 ### Removing tasks
 
 To remove a task, simply delete the item from the prd.yml file.
@@ -67,16 +69,6 @@ The following instructions should be done without interaction or asking for perm
 }
 \`\`\`
 
-## Important: Task sizing
-
-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 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.
-
 ${prdNotes}`
 
       const prompt = (options: {
@@ -88,6 +80,8 @@ The following instructions should be done without interaction or asking for
 permission.
 
 1. Your job is to complete the task with id \`${options.taskId}\` from the prd.yml file.
+   Read the entire prd.yml file to understand the context of the task and any
+   key learnings from previous work.
 2. Check if there is an existing Github PR for the task, otherwise create a new
    branch for the task.${options.targetBranch ? ` The target branch for the PR should be \`${options.targetBranch}\`. If the target branch does not exist, create it first.` : ""}
    - If there is an existing PR, checkout the branch for that PR.
@@ -99,15 +93,6 @@ permission.
    - When checking for PR reviews, make sure to check the "reviews" field and read ALL unresolved comments.
      Also read the normal comments to see if there are any additional requests.
 4. Implement the task.
-   - This session will time out after a certain period, so make sure to record
-     key information that could speed up future work on the task in the task
-     description. Record the information **in the moment** as you discover it,
-     do not wait until the end of the task. Things to record include:
-     - Important discoveries about the codebase.
-     - Any challenges faced and how you overcame them.
-     - APIs / libraries discovered that were useful.
-     - Links to relevant documentation.
-     - Any other information that could help future work on 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.
    ${sourceMeta.githubPrInstructions}
@@ -117,13 +102,27 @@ permission.
      permission to push branches, create PRs or create git commits.
 7. Update the prd.yml file to reflect any changes in task states.
    - Update the prd.yml file after the GitHub PR has been created or updated.
-   - Add follow up tasks only if needed.
-   - Append to the \`description\` field with any notes or important discoveries.
+   - Rewrite the notes in the description to include only the key discoveries
+     and information that could speed up future work on other tasks.
    - If you believe the task is complete, update the \`state\` to "in-review".
 
-**Remember:** record key information that could speed up future work on the task in
-the task description **in the moment** as you discover it, do not wait until
-the end of the task.
+## Important: Adding new tasks
+
+**If at any point** you discover something that needs fixing, or another task
+that needs doing, immediately add it to the prd.yml file as a new task.
+
+## Important: Recording key information
+
+This session will time out after a certain period, so make sure to record
+key information that could speed up future work on the task in the description.
+Record the information **in the moment** as you discover it,
+do not wait until the end of the task. Things to record include:
+
+- Important discoveries about the codebase.
+- Any challenges faced and how you overcame them.
+  - If it took multiple attempts to get something working, record what worked.
+  - If you found a library api was renamed or moved, record the new name.
+- Any other information that could help future work on similar tasks.
 
 ## Handling blockers
 
@@ -174,7 +173,7 @@ ${prdNotes}`
    - Make sure to research the codebase before creating the specification, to
      ensure it is relevant and feasible.
 2. Once you have saved the specification, your next job is to break down the
-   specification into smaller, manageable tasks.
+   specification into smaller, manageable tasks and add them to the prd.yml file.
    Each task should have a id of \`null\`, a title, and a concise description that
    includes a where to find the plan specification, a short summary of the task and a
    brief list of steps to complete it.
@@ -182,13 +181,12 @@ ${prdNotes}`
    - 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.
-   - **Never** create a research task. You should do all the necessary research
-     before creating the specification and tasks. Instead of creating a task like
-     "Research endpoints to refactor", investigate then endpoints first then create
-     tasks like "Implement user profile endpoint", "Refactor authentication endpoint", etc.
-3. Add the new or updated tasks to the prd.yml file.
-4. Wait until the tasks are saved, then setup task dependencies using the \`blockedBy\` field.
-5. Start a subagent with a copy of this prompt, to review the plan and provide feedback or improvements.
+   - If you need to add a research task, mention in the description that it needs to:
+     - add a specification file in the \`${options.specsDirectory}\` directory.
+     - add follow up tasks in the prd.yml file based on the new specification. The tasks
+       should reference the specification file in their description.
+3. Wait until the tasks are saved, then setup task dependencies using the \`blockedBy\` field.
+4. Start a subagent with a copy of this prompt, to review the plan and provide feedback or improvements.
 
 **Important:** You are only creating or updating a plan, not implementing any tasks yet.
 

package/src/cli.ts

@@ -15,7 +15,11 @@ import { Settings } from "./Settings.ts"
 import { run } from "./Runner.ts"
 import { plan } from "./Planner.ts"
 import { getOrSelectCliAgent, selectCliAgent } from "./CliAgent.ts"
-import { CurrentIssueSource, selectIssueSource } from "./IssueSources.ts"
+import {
+  CurrentIssueSource,
+  resetCurrentIssueSource,
+  selectIssueSource,
+} from "./IssueSources.ts"
 import { checkForWork } from "./IssueSource.ts"
 import { editPrd } from "./Edit.ts"
 import { createIssue } from "./CreateIssue.ts"
@@ -36,10 +40,21 @@ const specsDirectory = Flag.directory("specs").pipe(
   Flag.withDefault(".specs"),
 )
 
-const planMode = Command.make("plan", { specsDirectory }).pipe(
+const reset = Flag.boolean("reset").pipe(
+  Flag.withDescription("Reset the current issue source before planning"),
+  Flag.withAlias("r"),
+)
+
+const planMode = Command.make("plan", { specsDirectory, reset }).pipe(
   Command.withDescription("Iterate on an issue plan and create PRD tasks"),
-  Command.withHandler(plan),
-  Command.provide(CurrentIssueSource.layer),
+  Command.withHandler(
+    Effect.fnUntraced(function* (options) {
+      if (options.reset) {
+        yield* resetCurrentIssueSource
+      }
+      yield* plan(options).pipe(Effect.provide(CurrentIssueSource.layer))
+    }),
+  ),
 )
 
 const iterations = Flag.integer("iterations").pipe(