Context
PR #36 adds interim guidance to reqstool-conventions: MCP to read, YAML to edit, CLI only to verify — because the MCP server serves a spawn-time snapshot with no reload or staleness detection (reqstool/reqstool-client#437).
Follow-up
When reqstool/reqstool-client#437 is implemented, revise the "Tooling Division of Labor" section to the target state across all three interfaces:
- MCP: lookups and mid-loop verification (once its
verify/status answers are staleness-aware and carry gate semantics) — agents stop shelling out between edit iterations.
- CLI: remains the authoritative gate for CI and the final evidence run (exit code + reproducible output for evidence.md-style records).
- LSP (reqstool-client's planned LSP server): the in-editor surface — diagnostics for dangling
@Requirements/@SVCs references, go-to-definition between annotations and YAML, completion for requirement IDs; guidance should say what belongs in the editor loop vs the agent loop vs the gate.
The guidance should keep one principle constant: any status number must either be provably fresh or refuse to be a number.
🤖 Generated with Claude Code
Context
PR #36 adds interim guidance to reqstool-conventions: MCP to read, YAML to edit, CLI only to verify — because the MCP server serves a spawn-time snapshot with no reload or staleness detection (reqstool/reqstool-client#437).
Follow-up
When reqstool/reqstool-client#437 is implemented, revise the "Tooling Division of Labor" section to the target state across all three interfaces:
verify/status answers are staleness-aware and carry gate semantics) — agents stop shelling out between edit iterations.@Requirements/@SVCsreferences, go-to-definition between annotations and YAML, completion for requirement IDs; guidance should say what belongs in the editor loop vs the agent loop vs the gate.The guidance should keep one principle constant: any status number must either be provably fresh or refuse to be a number.
🤖 Generated with Claude Code