Research stage: bundled skill body (researchSkill.ts) + implement skill touch #213

New issue

david · 2026-08-16T21:52:17Z

david commented

2026-08-16 21:52:17 +00:00

Author the research stage's bundled skill body and the implementer touch:

src/skills/researchSkill.ts — the how-to body composed into the research stage system prompt (wrapper + body, per pi-loop's composition model — never native skill loading):
- Read the repo's design docs first (AGENTS.md, README, DESIGN.md, docs/) to understand what is being built.
- Pick the issue-relevant subset of the deterministic candidate deps (seeded with issue-context.json).
- Check docs/reference/<slug>/ first; update when the version gate flags staleness or coverage is insufficient for the issue; add when missing.
- GitHub-first fetching: prefer the dependency's GitHub repo (README, docs/, raw.githubusercontent.com); use SearXNG web_search to discover doc URLs when the repo/page is unknown.
- Write verbatim fetched pages (provenance headers) + _meta.json per docs/reference/<slug>/.
- Respect max-pages-per-dependency / max-deps-per-run caps.
- Do not close the issue; the docs PR is shipped by pi-loop, not the agent.
Implement skill touch — implementSkill.ts gains a short note telling the implementer to read docs/reference/<slug>/ for dependencies it touches (no behavioral change to implement's commit model).

References: ADR-014, DESIGN.md §3.1/§4, AGENTS.md stage anatomy.

Author the research stage's bundled skill body and the implementer touch: - **`src/skills/researchSkill.ts`** — the how-to body composed into the research stage system prompt (wrapper + body, per pi-loop's composition model — never native skill loading): - Read the repo's design docs first (AGENTS.md, README, DESIGN.md, docs/) to understand what is being built. - Pick the issue-relevant subset of the deterministic candidate deps (seeded with issue-context.json). - Check `docs/reference/<slug>/` first; update when the version gate flags staleness or coverage is insufficient for the issue; add when missing. - **GitHub-first** fetching: prefer the dependency's GitHub repo (README, docs/, raw.githubusercontent.com); use SearXNG `web_search` to discover doc URLs when the repo/page is unknown. - Write **verbatim fetched pages** (provenance headers) + `_meta.json` per `docs/reference/<slug>/`. - Respect `max-pages-per-dependency` / `max-deps-per-run` caps. - Do not close the issue; the docs PR is shipped by pi-loop, not the agent. - **Implement skill touch** — `implementSkill.ts` gains a short note telling the implementer to read `docs/reference/<slug>/` for dependencies it touches (no behavioral change to implement's commit model). References: ADR-014, DESIGN.md §3.1/§4, AGENTS.md stage anatomy.

david added the

pi-loop

label

2026-08-16 21:52:32 +00:00

Sign in to join this conversation.