SpeedyFoxAi/hermes-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

create-plan: v1.1.1 — fix tool names (web_extract/mcp__playwright__), echo metacharacter breakage, bash-wrapped tool calls, self-referential §6.2, add one-at-a-time rule

Browse Source
This commit is contained in:
Hermes Agent
2026-07-06 16:05:07 -05:00
parent 29556adb6f
commit fd3a71308e
3 changed files with 23 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
create-plan/references/ask-claude-validation-template.md
View File

@@ -89,48 +89,17 @@ The curator reads `<topic>_research.md` from disk and extracts **only the struct
## 3. The Dispatch Script (parameterized, ready to run)
**CRITICAL: Use `write_file`, not `echo` or `$(cat)` — shell metacharacters in the plan body (backticks, `$`, quotes) will break the command.** The prompt template is in §1 above. Compose it with `write_file`, then scp + run:
```bash
# 1. Build the prompt (see §1 for the full template)
PROMPT="==== PLAN BEGINS ====
$(cat <topic>_plan.md)
==== PLAN ENDS ====
# 1. Use write_file to create /tmp/curator-claude-prompt.txt
# Compose the prompt from §1, substituting <PLAN_BODY> and <RESEARCH_CLAIMS_EXTRACT>
# with the actual content. Do NOT use echo or $(cat) — use write_file.
==== RESEARCH CLAIMS/CITATIONS EXTRACT BEGINS ====
$(cat <research_claims_extract.md>)
==== RESEARCH CLAIMS EXTRACT ENDS ====
You are reviewing an evidence-diff for a software plan. Below is:
1. The plan in full.
2. An extract of the structured claims, version numbers, official-URL
citations, and key code/config snippets from the research evidence.
CRITICAL CONSTRAINT: Do NOT propose new features, new architecture, or new complexity.
Your job is to find FLAWS in what's already proposed — not to add more. If you find
a problem, say what's wrong and suggest the SIMPLEST fix.
YOUR JOB IS AN EVIDENCE-DIFF, NOT A VIBE CHECK.
For each claim the plan makes, check whether the provided research extract supports it.
For each claim in the provided research extract, check whether the plan addresses it.
Specifically report:
- Plan assertions that the research extract does NOT support (hallucinated claims)
- Major research extract findings the plan OMITS (silent gaps)
- Internal contradictions in the plan
- Missing TDD discipline (failing test before code-producing task?)
- Tasks larger than 2-5 minutes of focused work
- Missing official doc citations for tools the plan uses
Report format:
- Release-blockers (must fix)
- Medium (should fix)
- Low (nice to have)
- Pass-criteria met / not met
Do not rewrite the plan. Just report findings."
# 2. Write locally → scp to remote → run via ask.sh (file-based, no shell escaping)
echo "$PROMPT" > /tmp/curator-claude-prompt.txt
# 2. scp the file to the remote
scp -i ~/.ssh/id_ed25519 -o StrictHostKeyChecking=accept-new -o ServerAliveInterval=30 /tmp/curator-claude-prompt.txt n8n@10.0.0.28:/tmp/curator-claude-prompt.txt
# 3. Run ask.sh on the remote
RESP=$(ssh -i ~/.ssh/id_ed25519 -o StrictHostKeyChecking=accept-new -o ServerAliveInterval=30 n8n@10.0.0.28 '~/claude/hermes_support/ask.sh --qfile /tmp/curator-claude-prompt.txt')
echo "$RESP"
rm -f /tmp/curator-claude-prompt.txt