Re-design choices in New Project #115

Closed
opened 2026-10-01 22:49:37 -04:00 by cmoriarty · 1 comment
Owner

The current choices don't really feel complete. Ultimately I would like choices that cover:

  1. Plan a multi-braid-session project by creating Forgejo issues or using a markdown plan, with a checkbox to begin first issue/task, and a checkbox to auto-plan (otherwise the user will be asked clarifying questions interactively).

"Plan Project"

  1. Plan a single one-shot braid project AND implement it in a single braid run. Checkbox for Minimum Viable Product (MVP) as a way to just assess feasibility of an idea, otherwise Braid will do its best to finish everything in one session. Actually, lets make "create and track a PLAN.md, or create and track Forgejo issues" checkboxes.

"One-shot"

  1. Lastly, I would like to have an option to actually implement multi-braid-session planned projects, perhaps another checkbox to fully complete project with replanning. If my experience as a software engineer has taught me anything is that plans will need to change/update as the implementation progresses. So I think this mode actually needs some research and design decide how to have a new "review and update plan" step after finishing an issue, but before starting a new session. I think this overlaps with #11, as github spec kit I believe is in itself a framework of planning and development that could possible also be automated (Ive just never used it myself)

image

The current choices don't really feel complete. Ultimately I would like choices that cover: 1. Plan a multi-braid-session project by creating Forgejo issues or using a markdown plan, with a checkbox to begin first issue/task, and a checkbox to auto-plan (otherwise the user will be asked clarifying questions interactively). "Plan Project" 2. Plan a single one-shot braid project AND implement it in a single braid run. Checkbox for Minimum Viable Product (MVP) as a way to just assess feasibility of an idea, otherwise Braid will do its best to finish everything in one session. Actually, lets make "create and track a PLAN.md, or create and track Forgejo issues" checkboxes. "One-shot" 3. Lastly, I would like to have an option to actually implement multi-braid-session planned projects, perhaps another checkbox to fully complete project with replanning. If my experience as a software engineer has taught me anything is that plans will need to change/update as the implementation progresses. So I think this mode actually needs some research and design decide how to have a new "review and update plan" step after finishing an issue, but before starting a new session. I think this overlaps with #11, as github spec kit I believe is in itself a framework of planning and development that could possible also be automated (Ive just never used it myself) ![image](/attachments/42e6596b-7b11-4d95-bc38-7d8a94d70bf3)
Author
Owner

Shipped as two changes, new-project-approaches and plan-to-completion.

New Project asks for an approach:

  • Plan Project plans a multi-run project as PLAN.md and Forgejo issues. Its choices: Auto-plan (no clarifying questions), Track as Forgejo issues, Begin the first item, and Complete the project.
  • One-shot plans and implements in one run. Its choices: MVP (scope the brief to the smallest version that proves the idea), Track in PLAN.md, and Track as Forgejo issues. A one-shot that tracks lists its task groups as pieces: in PLAN.md, or as issues in a milestone that close when the run merges.

Complete the project (mode 3, first version). PLAN.md says Run to completion: yes in its head, so stopping it is a one-line edit. After each item's run:

  • plan.replan reviews and rewrites the rest of the plan from what the run did, with no questions. Its notes go into the pull request.
  • git.commit.replan syncs the OpenSpec changes and files new items.
  • plan.next closes dropped items' issues and starts the next item, one at a time per repository.
  • When Now is all ticked, Next becomes the new Now.

Verified. The fast and full lanes passed on the integrated batch (3,388 backend tests, 681 vitest, 249 browser specs with the slow and live ones, 29 of 29 simulated runs), and it is live on production as 57971c2 (deploy run 138, self-check braid-selfcheck: ok). Archived in a6ae0dc. New simulated runs: plan-chosen-up-front, one-shot-tracked and plan-to-completion. On production, New Run shows Approach with both choices and Complete the project.

Not yet done:

  • A real chain on production: two items landing and a replan changing the plan. It takes hours and merges into the repository, so it waits for your go.
  • Rewording an existing issue when a replan changes an item: v1 comments the new text instead.
  • Showing the approach on the run page: it would need a schema migration.
  • GitHub Spec Kit was background only.
Shipped as two changes, `new-project-approaches` and `plan-to-completion`. **New Project asks for an approach:** - **Plan Project** plans a multi-run project as PLAN.md and Forgejo issues. Its choices: Auto-plan (no clarifying questions), Track as Forgejo issues, Begin the first item, and Complete the project. - **One-shot** plans and implements in one run. Its choices: MVP (scope the brief to the smallest version that proves the idea), Track in PLAN.md, and Track as Forgejo issues. A one-shot that tracks lists its task groups as pieces: in PLAN.md, or as issues in a milestone that close when the run merges. **Complete the project (mode 3, first version).** PLAN.md says `Run to completion: yes` in its head, so stopping it is a one-line edit. After each item's run: - `plan.replan` reviews and rewrites the rest of the plan from what the run did, with no questions. Its notes go into the pull request. - `git.commit.replan` syncs the OpenSpec changes and files new items. - `plan.next` closes dropped items' issues and starts the next item, one at a time per repository. - When Now is all ticked, Next becomes the new Now. **Verified.** The fast and full lanes passed on the integrated batch (3,388 backend tests, 681 vitest, 249 browser specs with the slow and live ones, 29 of 29 simulated runs), and it is live on production as 57971c2 (deploy run 138, self-check `braid-selfcheck: ok`). Archived in a6ae0dc. New simulated runs: `plan-chosen-up-front`, `one-shot-tracked` and `plan-to-completion`. On production, New Run shows Approach with both choices and Complete the project. **Not yet done:** - A real chain on production: two items landing and a replan changing the plan. It takes hours and merges into the repository, so it waits for your go. - Rewording an existing issue when a replan changes an item: v1 comments the new text instead. - Showing the approach on the run page: it would need a schema migration. - GitHub Spec Kit was background only.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#115
No description provided.