cmoriarty/braid
1
0
Fork 0
Code Issues 15 Pull requests Projects Releases Packages 1 Wiki Activity Actions

Re-design choices in New Project #115

New issue
Open
opened 2026-10-01 22:49:37 -04:00 by cmoriarty · 0 comments
cmoriarty commented 2026-10-01 22:49:37 -04:00
Owner
Copy link

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)
image.png
39 KiB
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
archive/prefect-kestra-experiments
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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.