governance: zero technical debt, production-ready always; safety first across system prompts, AGENTS templates, proposal, and plan

This commit is contained in:
2025-09-17 10:31:25 -05:00
parent ff33cb282a
commit fae0f5b413
11 changed files with 72 additions and 16 deletions

View File

@@ -15,3 +15,9 @@
-- Governance/Propagation --
- When given a reusable, non-project-specific rule, update: global system prompt (both files), seed AGENTS templates (`meta/AGENTS.seed.*`), and project AGENTS template (`templates/project/_shared/AGENTS.md`).
- Also fold into proposal/plan so scaffolding includes it, and log in DevLog.
-- Zero Technical Debt, Production-Ready --
- Safety first, speed second. No technical debt ever; always production-ready.
- No deferring tests/docs/refactors needed for clarity/maintainability.
- TDD by default (tests first). Keep docs current.
- Use sub-agents/parallelization to maintain quality and speed.

View File

@@ -75,6 +75,15 @@ You are a coding agent running in the Codex CLI (terminal-based). Be precise, sa
- Log the change in `docs/devlog/` with context and rationale.
- Treat these updates as allowed out-of-band edits when explicitly directed by the user.
## Zero Technical Debt, Production-Ready Always
- Safety first, speed second. Never compromise correctness, security, or data safety.
- No technical debt allowed at any time. Every commit must be production-ready.
- No deferring of tests, documentation, or refactors required for clarity/maintainability.
- Follow TDD: write failing tests first; make them pass; refactor.
- Keep documentation (README, docs/wrapper.md, DevLogs) current with changes.
- Code must be clean, maintainable, and consistent with project style.
- Use multiple/sub-agents or parallelization if needed to maintain quality and speed.
## Exceptions
- Only bypass the questions→proposal→plan cycle when the user explicitly directs you to do so (and log that exception in the dev log).