TSYSGroupCorporate/TSYSGroupAIOS
Template
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(policy): ban harness question tools — questions-v(N).md only

Browse Source 
Harness "ask user"/question tools (structured prompts, modal forms) are
not portable across harnesses, don't version history, and bypass the
git-tracked record. Make the existing questions-v(N).md rule explicit
and non-negotiable in both BASELINE-PROMPT.md §10 and AGENTS.md.

💘 Generated with Crush

Assisted-by: Crush:glm-5.2
This commit is contained in:
mrcharles
2026-08-10 16:03:57 -05:00
parent 323e8ce2d1
commit 29f33c4b03
2 changed files with 15 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+6
View File
@@ -123,6 +123,12 @@ docker run --rm --env-file ~/.creds/discourse.env \
## Questions
- **NEVER use a harness "question"/"ask user" tool** (structured prompts,
modal forms, tabbed questions). Banned across every project, every
harness. Not portable, not version-controlled, bypasses the git record.
Non-negotiable. (See `BASELINE-PROMPT.md` §10.)
- **All questions go in the git-tracked `questions-v(N).md` file.** The
human edits the answer inline in the same file; version up per round.
- Capture questions for the human in a git-tracked `questions-v(N).md` file.
- The human reviews and edits it inline. Version up when a round of answers lands.
- Questions, answers, and the reasoning behind decisions are often more important than the code. Synthesize resolved Q&A into Discourse (decisions) and Redmine (work items).
BASELINE-PROMPT.md
+9 -1
View File
@@ -97,7 +97,15 @@ do not require per-change Redmine approval.
## 10. Questions file — `questions-v(N).md`
- Capture questions in a git-tracked, versioned file: `questions-v1.md`, `questions-v2.md`, …
- **NEVER use a harness "question"/"ask user" tool** (structured prompts,
modal forms, tabbed questions, etc.). Ever. They are banned across every
project. They are not portable across harnesses, they don't version
history, and they bypass the git-tracked record. This is non-negotiable.
- **All questions go in the git-tracked `questions-v(N).md` file.** Write
the question; the human edits the answer inline in the same file. This
preserves history, works under every harness, and keeps reasoning next
to the answer. Version up (`questions-v2.md`, …) when a round lands.
- Capture questions in a versioned file: `questions-v1.md`, `questions-v2.md`, …
- The human reviews and edits it inline. Version it when a round of answers goes in.
- Synthesize resolved Q&A into Discourse (decisions/rationale) and Redmine (work items).