diff --git a/QUESTIONS.md b/QUESTIONS.md new file mode 100644 index 0000000..8f828aa --- /dev/null +++ b/QUESTIONS.md @@ -0,0 +1,33 @@ +# Open Questions + +These questions will guide the initial design and implementation. Please answer inline. + +## Repo & workflow +1. Git remote: Should we push to an existing remote? If yes, please provide the remote URL and branch (default `origin main`). +2. Tagging: Use `YYYY-MM-DD-HHMM` in local time or UTC? Use `tea` only for tagging/releases, or also for pushes? +3. Commit cadence: Any specific commit style (e.g., Conventional Commits)? + +## codex-cli wrapper +4. codex-cli path: How is `codex`/`codex-cli` invoked in your environment (command name, install path)? +5. Defaults: Preferred default model, token budget, and reasoning level? +6. Config precedence: Order of overrides? (e.g., CLI flags > env vars > project config > mode config > global defaults) +7. Config files: Desired locations/names? (e.g., `.codexrc`, `.codex/mode.yaml`, `project.yaml`) +8. Prompts storage: Where to store Global System Prompt, Mode Prompt, and Project Prompt? (proposal: `modes//system.md`, `modes//mode.md`, `projects//prompt.md`) +9. MCP configuration: Expected format and location? (JSON/YAML/TOML; per-mode vs per-project) + +## Wizards +10. Mode wizard fields: Minimum fields for a mode (name, description, defaults, prompts, MCP config)? Any templates you prefer? +11. Project wizard fields: Minimum fields for a project (name, path, project prompt, default mode, overrides)? + +## Execution behavior +12. Mode selection: CLI flags `--mode`, `--project`, and optional `--prompt-file` acceptable? +13. Non-interactive: Should wrapper fully resolve configs non-interactively by default, with an `--interactive` flag for wizard-like prompting? +14. Output handling: Where to log transcripts or runs? (proposal: `runs//…`) +15. Safety: Any commands that must never be executed without confirmation? + +## Misc +16. Licensing/headers: Any repo-specific requirements beyond the existing LICENSE? +17. Supported OS/shells: Target bash/zsh on macOS/Linux, anything else? + +Once answered, I will draft a concise proposal and then a concrete implementation plan for review. + diff --git a/SeedPrompt.md b/SeedPrompt.md new file mode 100644 index 0000000..570843b --- /dev/null +++ b/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 .md and .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. \ No newline at end of file diff --git a/devlog/DEVLOG_HUMAN.md b/devlog/DEVLOG_HUMAN.md new file mode 100644 index 0000000..91bbe3e --- /dev/null +++ b/devlog/DEVLOG_HUMAN.md @@ -0,0 +1,19 @@ +# Development Log (Human Readable) + +Date: 2025-09-17 08:55 (UTC) + +Summary: +- Bootstrapped collaboration scaffolding based on SeedPrompt.md. +- Created dev logs (LLM-optimized and human-readable) and a QUESTIONS.md file. + +Details: +- Rationale: Establish clear, file-based collaboration channels (logs + questions) with minimal noise in chat. +- Scope: No functional code yet; this is setup to enable fast iteration. + +Next Steps: +- Collect answers in QUESTIONS.md. +- With clarifications, propose initial design and plan for the wrapper script (crawl phase). + +Notes: +- Tagging a release and using `tea` is deferred until we have a first runnable wrapper or as directed. + diff --git a/devlog/DEVLOG_LLM.md b/devlog/DEVLOG_LLM.md new file mode 100644 index 0000000..c3cb33b --- /dev/null +++ b/devlog/DEVLOG_LLM.md @@ -0,0 +1,15 @@ +# Dev Log (LLM-Optimized) + +This log is concise and structured for quick machine parsing and summarization. One entry per session/change. + +## 2025-09-17T08:55Z +- context: Initialized collaboration per SeedPrompt.md +- actions: + - Added `devlog/DEVLOG_LLM.md` and `devlog/DEVLOG_HUMAN.md` + - Added `QUESTIONS.md` to drive collaboration +- decisions: + - Defer tagging a release until first runnable wrapper exists +- next: + - Await answers in `QUESTIONS.md` + - Draft proposal and implementation plan once clarified +