chore: scaffold devlog and QUESTIONS; capture SeedPrompt.md

SeedPrompt.md

@@ -0,0 +1,36 @@
+(We are in a codex-cli session and i've instructed it to read this file but given it no other instructions)
+
+
+## Meta Rules
+
+- Please keep a development log of your work (In both llm optimized form and human readable form ) (separate files) (in a subdirectory called devlog)
+- Please commit frequently and push/tag a release (YYYY-MM-DD-HHMM) (using the tea command) when you feel it's warranted (all work is done on main for now)
+- Please create and maintain README.md and a docs/ directory with <feature>.md and <adr-feature>.md as we go
+- Please create and maintain unit tests as we go in a tests/ directory
+
+
+## Ultimate goal of this project
+
+A wrapper bash script around codex-cli allowing the use of "modes" which will be a collection of 
+
+- A fixed Global system prompt 
+- A fixed Mode  prompt
+- A variable (user defined) project specific prompt
+- Codex settings (model/token budget/reasoning level etc)
+- MCP configuration
+
+Also:
+
+- A "wizard" to create new modes (by filling out a markdown file intake form)
+- A "wizard" to create new projects (by filling out a markdown file intake form)
+
+## Approach
+
+Lets "crawl/walk/run" , starting with a simple wrapper script for codex-cli that has (documented) defaults set but also allows (via command line flags/environment variables/config file) over-riding the options 
+
+This should be very collaborative. Ask questions (in a markdown file), once they are answered then create a proposal for review/approval, then create a plan for review/approval. Then once everything is approved, implement the code for review and approval.
+
+I want to be able to test the code early/often and be able to provide feedback. I want to be able to edit markdown files inline to provide context/ask questions etc as we go. The chat interface itself should be kept very clean as it's running in the bottom of my vscode instance and I want to use vscode markdown facilities to rapidly read/edit the markdown files. So our primary way of interacting
+will be via those files.
+
+Commit/push everything in the repo now before we get started on the project.