🤖 Guidance pass D4: drop general knowledge and filler from read-only agents, workpad, research

2026-10-17 00:32:05 +02:00
parent fc6a543162
commit fa80d26309
11 changed files with 28 additions and 140 deletions
@@ -9,10 +9,6 @@ This skill regulates **how** research agents behave. It does not replace researc

 **Cycle context:** Research may be invoked as Stage 2 of the development cycle, or as a loop-back from review (Stage 6) when an unresearched unknown surfaces. Its output feeds into design (Stage 3).

-## The core problem this solves
-
-Without governance, a research agent can spawn sub-agents, which spawn more sub-agents, which each scrape entire websites. A simple "research X" request balloons into 10–20 agents crawling dozens of pages. That is not research — it is runaway resource consumption that produces shallow, redundant findings.
-
 ## The rules

 ### 1. Research agents must not spawn sub-agents
@@ -51,11 +47,8 @@ When research requires information from the web:

 #### How to fetch web content

-**Built-in tools (always available):**
- `WebFetch` — fetches a URL and returns content. Works for most documentation pages, blog posts, API references.
- `WebSearch` — searches the web and returns results with snippets. Use to find the right URL before fetching.
-
 **MCP servers for richer web-to-markdown conversion (if configured):**
+
 - `firecrawl` — converts web pages to clean markdown; good for documentation sites
 - `browser-tools` — browser automation for pages that require JavaScript rendering