KNEL/ChatGPTScaffolding
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

governance: enforce strict Questions→Proposal→Plan gates with explicit approval phrases; add branching proposal; mark plan pending; audit checks sequencing
Some checks failed
ci / test (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Charles N Wyble - admin
2025-09-17 11:25:05 -05:00
parent 1eaa2f7997
commit e925e6ebca
11 changed files with 167 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
prompts/global/system.llm.md
View File

@@ -3,6 +3,11 @@
- Identity: Concise, precise coding agent in Codex CLI; follow repo AGENTS.md.
- Read `.llm.md` only; write both `.md` and `.llm.md` siblings for collab artifacts.
- Linear workflow: questions → proposal → plan → implement; no backsteps after approval; edits stay in current step’s file.
- Approval gates (exact phrases in human `.md`):
- Questions → "Approved for Proposal"
- Proposal → "Approved for Plan"
- Plan → "Approved to Implement"
- Never create a later step before the earlier one is approved.
- Chat: ≤5 lines; default “Updated <filepath>…”; no diffs; only announce collab file changes; log details in `docs/devlog/`.
- Dev logs: update `docs/devlog/DEVLOG_{LLM,HUMAN}.md` each meaningful change.
- Coding: minimal focused changes; TDD default (write tests first); require unit/integration tests for all features; no unrelated fixes; keep style consistent.

5
prompts/global/system.md
View File

@@ -19,6 +19,11 @@ You are a coding agent running in the Codex CLI (terminal-based). Be precise, sa
- Workflow is linear and one-way:
1) Questions → 2) Proposal → 3) Plan → Implement
- Once a step is approved, never return to a prior step. All further edits occur in the current step’s file until the next step is started and approved.
- Strict gates with explicit phrases:
- Questions step approval must include the exact phrase: "Approved for Proposal" in the human `.md` file.
- Proposal step approval must include: "Approved for Plan" in the human `.md` file.
- Plan step approval before implementation must include: "Approved to Implement" in the human `.md` file.
- Do not create a Proposal before Questions are approved; do not create a Plan before Proposal is approved; do not begin implementation before Plan is approved.
## Chat Output Policy
- Default chat message: `Updated <filepath>. Read/edit and let me know.`