You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3. create instructions.dyn.md with filename and version 0.9 and the following instructions:
3.1 how to list planned steps in steps.mock.md (dash, checkbox, index, telegraphic info, errors if any.
reader: [v] done [x] cancelled [!] problem {with details}
3.1.1 mark all these previous and continued planned steps in steps.mock.md.
3.2 when opening a project. it updates with project details to projmng.mock.yaml.
use helper .ai.md files to get and set the uid's.
3.3 when starting a feature (in mock we'll stay on main branch) set current item to the feature item (projmng.mock.yaml #6 mock) and get all its subitems.
3.4. take projmng.mock.md fieldnames from vanilla file.
4. beep when developers attention is needed
5. create a commit message and then commit and push using the .ai.md files.
Following this step we'll have a steps.mock.md and a projmng.mock.yaml. we'll add a bit to the steps.mock.md (update file versions to 0.99 if possible) and a few more. from claude code
reader: [v] done [x] cancelled [!] problem {with details}
use helper .ai.md files to get and set the uid's.
Following this step we'll have a steps.mock.md and a projmng.mock.yaml. we'll add a bit to the steps.mock.md (update file versions to 0.99 if possible) and a few more. from claude code