**Parent:** [#1](https://github.com/pashute/binabase/issues/1) feature/simpleRun
## rename and unify. --
#1. We will only have *.dynai.md files.
1.1 *.dynai.md files are Dynamait files: Files with clear sequences of instructions for the ai conversation and actions through the console. each step with its inputs and outputs.
Some steps need to made in several sub-step sequences.
1.2 The dynai files must be readable and clear to humans, in sections with remarks.
1.3 under the CMD there will be no files named instructions....md and no *.fs1 files.
meaning markdown files with very clear instruction sequences for the AI, including powershell commands inside.
#2 File creatiion and overview
2.1 Creating each file, needs explicit separate ok from developer before ai creates it.
2.2 After creating the file the ai will discuss its contents through as many iterations as needed with the developer till he is satisfied.
2.3 Each of these dyanai files has main steps and sub-steps
2.4 Each step has input parameters and outputs
2.5 Each step has a specified discussion structure before and after.
2.6 During testing the steps will be done one after the other with a stop for developer approval.
2.7. Upon failure the sequence will be stopped and the user will be notified with a suggestion of how to fix.
2.8. The powershell commands will be gh (github) commands but not the query language.
#3 Use and update the projdev.yaml
with the following structure.
Note: `id` fields (GH node IDs) are blank — those need the `gh` command to fetch. Want me to write that fetch command now?
#4 .dynai files:
- [ ] Create *.dynai.md files (the numbers are part of the name)
- `1a.StartFeature.dynai.md`
- // checks that previous feature branch was closed. that we are in develop.
- // then confirms with user to proceed,
- // creates and moves to new feature branch off develop and updates
- `1b.EndFeature.dynai.md`
- // checks that all is committed, closed and pushed to gitflow feature branch on github
- // merges with the gitflow develop branch of our project and verifies is merged via gh command.
- // if all ok, shows results to developer, asks for developer's ok
- // if approved deletes feature branch with gh command
- // verifies deleted with gh command, reviews result with developer.
- `2a.StartItem.dynai.md` // input: item number.
// # Start working on gh-proj issue
// gh command Looks for issue (by url) in gh proj.
// confirms title with user
// then updates /dev/ai/projdev.yaml
// and confirms the item's steps (task checkboxes) with user,
// then updates steps.md and proceeds step by step
- `2b.EndItem.dynai.md` //
// check that all steps in item are completed.
// check that all files committed and pushed or changes deferred for other item
// anything not committed and pushed, confirm with user and on ok commit and push.
// add to item closing note in projdev.yaml (commit num, title, link, description see 3.commit)
- `3.Commit`
// verify correct iteration, branch and item (head, parent and current if any different)
// if no push specified, verify if push desired as well
// create message: item number and link, title, item steps accomplished, changes (text) and filechanges (filename path and changetext)
// get developer confirmation
// on ok, update projdev.yaml
// commit and verify with gh command
// discuss results with developer.
- [ ] User review and test each stage of the dynai.md files (awaiting OK)
order of files 1a, 2a, 3, 2b, 1b
- [ ] Each step needing review list in steps.md
- [ ] Each step reviewed, after user's ok tick off with v
- [ ] Close #9 after review
- [ ] Return to [#8](https://github.com/pashute/binabase/issues/8)
markdown