dogma: Skill for Claude Code

Secondary Research Sprint

Governing axiom: Endogenous-First (MANIFESTO.md § 1)

This skill encodes a 5-step procedure for executing secondary research sprints on bare-bones GitHub issues that contain only a title and a URL. All steps are governed by AGENTS.md § Agent Communication and § Programmatic-First Principle. Read AGENTS.md before modifying any step.

When to use: An issue arrives with just a URL and no acceptance criteria, no summary, and no context. This skill enriches the issue first, checks the existing corpus for coverage, scouts the target source, synthesizes a D4 doc, and archives the result.

When NOT to use: Full multi-source research topics (use deep-research-sprint); issues that already have a detailed brief; single-source lookups that don't warrant a D4 doc.

---

Step 1 — Issue Enrichment (before anything else)

Fetch the URL in the issue body and rewrite the issue with structured context before any research begins.

Check before fetch (Algorithms-Before-Tokens: avoid re-downloading cached content):

uv run python scripts/fetch_source.py <url> --check

Fetch if not cached:

uv run python scripts/fetch_source.py <url>

Extract from the fetched content:

• Title
• Abstract or summary (3–5 sentences)
• Key claims (3–5 bullets)
• Any recommended follow-up reads

Write enriched issue body to a temp file (using create_file or inline write — never heredoc):

Body template:

# <Title from source>

**Source:** <URL>
**Fetched:** <date>

## Summary
<3-5 sentence summary>

## Key Claims
- <claim 1>
- <claim 2>
- ...

## Relevance to dogma
<1-2 sentences on why this matters for the project>

## Acceptance Criteria
- [ ] D4 synthesis doc committed at `docs/research/<slug>.md`
- [ ] Issue closed with `Closes #<num>` in PR or via `gh issue close`
- [ ] `validate_synthesis.py` passes on the output doc

Validate before posting:

test -s /tmp/issue_<num>_enriched.md && file /tmp/issue_<num>_enriched.md | grep -q "UTF-8\|ASCII"