* docs: clarify capture_thought is an optional convention (#1873) Issue #1873 merged /gsd:extract-learnings with an optional capture_thought hook, but the docs never explained what the tool is or where it comes from — readers couldn't tell whether it was a bundled GSD tool, a required dependency, or something they had to install. This surfaced in a user question on that issue's thread. Clarify in docs/FEATURES.md §112 and the workflow file that capture_thought is a convention — any MCP server exposing a tool with that name will be used; if none is present, LEARNINGS.md remains the primary output and the step is a silent no-op. No behavioral change. All 23 extract-learnings tests still pass. * fix(security): add human to detection message; test [/INST] closing form neutralization - Detection message now lists <human> alongside <system>/<assistant>/<user> - Sanitizer regex extended to cover [/INST] closing form (was only [INST]) - Detection pattern extended to cover [/INST] closing form - New sanitizeForPrompt test asserts [/INST] is neutralized Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(config): add workflow.security_* keys to VALID_CONFIG_KEYS Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs: add language tag to fenced code block in FEATURES.md Fixes MD040 lint finding in PR #2379 — the capture_thought tool signature example was missing a javascript language identifier. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Tom Boucher <trekkie@nomorestars.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -95,7 +95,11 @@ Each surprise entry must include:
|
||||
</step>
|
||||
|
||||
<step name="capture_thought_integration">
|
||||
If the `capture_thought` tool is available in the current session, capture each extracted learning as a thought with metadata:
|
||||
**What this step is:** `capture_thought` is an **optional convention**, not a bundled GSD tool. GSD does not ship one and does not require one. The step is a hook for users who run a memory / knowledge-base MCP server (for example ExoCortex-style servers, `claude-mem`, or `mem0`-style servers) that exposes a tool with this exact name. If any MCP server in the current session provides a `capture_thought` tool with the signature below, each extracted learning is routed through it with metadata. If no such tool is present, the step is a silent no-op — `LEARNINGS.md` is always the primary output.
|
||||
|
||||
**Detection:** Check whether a tool named `capture_thought` is available in the current session. Do not assume any specific MCP server is connected.
|
||||
|
||||
**If available**, call once per extracted learning:
|
||||
|
||||
```
|
||||
capture_thought({
|
||||
@@ -106,7 +110,7 @@ capture_thought({
|
||||
})
|
||||
```
|
||||
|
||||
If `capture_thought` is not available (e.g., runtime does not support it), gracefully skip this step and continue. The LEARNINGS.md file is the primary output — capture_thought is a supplementary integration that provides a fallback for runtimes with thought capture support. The workflow must not fail or warn if capture_thought is unavailable.
|
||||
**If not available** (no MCP server in the session exposes this tool, or the runtime does not support it), skip the step silently and continue. The workflow must not fail or warn — this is expected behavior for users who do not run a knowledge-base MCP.
|
||||
</step>
|
||||
|
||||
<step name="write_learnings">
|
||||
|
||||
Reference in New Issue
Block a user