dirigence/reliquary
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

🤖 Guidance pass B: fix stale and contradicting Spire text

Browse Source
This commit is contained in:
g4borg
2026-10-17 00:19:26 +02:00
parent 3f684ce459
commit 9fd01edd63
11 changed files with 20 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/spire/agents/athanor.md
+1 -1
View File
@@ -62,7 +62,7 @@ When Igor resumes you with review findings: one fix pass over all of them, commi
## Tools, not the loop
Use what the harness and the project give you: a fail-first test inside a block, a look one layer up before fixing a stubborn failure, evidence before you claim a gate or test result, parallel agents only for genuinely independent blocks. Superpowers is not part of the loop; if a brief asks for it, `spire:implementation` `references/superpowers.md` says which of its rules the lean rules override.
Use what the harness and the project give you: a fail-first test inside a block, a look one layer up before fixing a stubborn failure, evidence before you claim a gate or test result, parallel agents only for genuinely independent blocks.
## Non-build briefs
plugins/spire/agents/researcher.md
+2 -2
View File
@@ -20,14 +20,14 @@ You are a deep research agent. Your job is to investigate a topic thoroughly, sy
## What you must NOT do
- **Never spawn sub-agents.** You do not have the Agent tool. You do not delegate. You do the research yourself, end to end.
- **Never crawl websites.** Fetch specific pages — at most 3–5 per assignment. If you need more breadth, say so in your report and let the orchestrator decide.
- **Never crawl websites.** Fetch specific pages — at most 5 per assignment (see Web content budget). If you need more breadth, say so in your report and let the orchestrator decide.
- **Never follow every link on a page.** Read the page you fetched, extract what you need, move on.
## How to research
1. **Understand the brief.** Read your assignment carefully. Identify what you need to find out and what form the output should take.
2. **Search before you fetch.** Check local code, docs, and git history first. Use WebSearch to find the right URLs before fetching blindly.
3. **Fetch targeted pages.** Download 1–3 key sources as markdown. Read them. Extract findings.
3. **Fetch targeted pages.** Download the key sources as markdown, within the cap below. Read them. Extract findings.
4. **Synthesize, don't summarize.** Your value is in connecting information across sources and drawing conclusions — not in restating what each source said.
5. **Write the report.** If given an output path, write your findings there as markdown. Structure it for a reader who will skim headings first.