KNEL/PFVCluster
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(agents): clarify questions-v(N).md versioning — increment on each answer round

Browse Source 
💘 Generated with Crush

Assisted-by: Crush:glm-5.2
This commit is contained in:
mrcharles
2026-08-11 19:49:46 -05:00
parent 6683c8c892
commit 1f634a6aa0
1 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+8 -5
View File
@@ -102,7 +102,7 @@ traceable to an approved ticket. There is no "I thought it would help."
1. **Set up the environment:** `bash scripts/setup-hooks.sh` (installs git hooks — idempotent). 1. **Set up the environment:** `bash scripts/setup-hooks.sh` (installs git hooks — idempotent).
2. **Read this file** (`AGENTS.md`) — project policy and domain knowledge. 2. **Read this file** (`AGENTS.md`) — project policy and domain knowledge.
3. **Read [questions-v1.md](questions-v1.md)** — open questions awaiting human input. 3. **Read the latest questions file** (`questions-v*.md`) — open questions awaiting human input. The version number increments each round (v1, v2, v3...).
4. **Check for understanding — GATE.** In your own words, summarize ALL the rules 4. **Check for understanding — GATE.** In your own words, summarize ALL the rules
back to the user before doing any work: Agent Authority (ticket-governed, back to the user before doing any work: Agent Authority (ticket-governed,
propose-never-implement), Access-Channel SSH-only policy, Remote access propose-never-implement), Access-Channel SSH-only policy, Remote access
@@ -164,10 +164,13 @@ for a full audit or `--fast` for pre-commit speed. Bypass with `--no-verify`
**NEVER use a harness "question"/"ask user" tool** (structured prompts, **NEVER use a harness "question"/"ask user" tool** (structured prompts,
modal forms, tabbed questions). Banned across every project, every harness. modal forms, tabbed questions). Banned across every project, every harness.
They are not portable, not version-controlled, and bypass the git record. They are not portable, not version-controlled, and bypass the git record.
**All questions go in [questions-v1.md](questions-v1.md)** — write the **All questions go in the current `questions-v(N).md` file** — write the
question; the human edits the answer inline in the same file. Version up question; the human edits the answer inline in the same file. **Version up
per round. Synthesize resolved Q&A into Discourse (decisions) and Redmine the filename each time answers land** (v1 → v2 → v3...): create
(work items). See `BASELINE-PROMPT.md` §10. `questions-v2.md` with resolved Q&A marked, new questions appended. This
preserves the history of each Q&A round. Synthesize resolved Q&A into
Discourse (decisions) and Redmine (work items). See `BASELINE-PROMPT.md`
§10.
## Documentation policy (IMPORTANT) ## Documentation policy (IMPORTANT)