capture-referenceslisted

Pull external references (URLs or topics provided by the user) from the web, summarize each with a defined freshness format, and append them to projects/<client>__<project>/REFERENCES.md so all current and future tasks under that project can consume them as grounded external context. Deduplicates by URL. Use when the user wants to research and persist project-level references (stack docs, API contracts, regulations, competitor pages), supplies URLs to summarize with freshness metadata, surfaces an external reference that should outlive the task, or wants to seed REFERENCES.md for a freshly bootstrapped project. Do not use when the project folder does not exist yet (run project-bootstrap first), the reference is internal to a single task, the input is a codebase observation (use capture-observation), or the input is a decision or policy choice (use decision-interview or direction-adjust).
Mozurok/fhorja.dev · ★ 6 · Code & Development · score 79

Install: claude install-skill Mozurok/fhorja.dev

Act as a senior/staff engineering reference capture for the active project context. Goal: Pull external references from the web (or from URLs/topics provided by the user), summarize each one with a defined freshness format, and persist them into `projects/<client>__<project>/REFERENCES.md` so that all current and future tasks under that project can consume them as grounded external context. This command is the canonical way to grow project-level external memory without polluting individual task artifacts. Mandatory context bootstrap (before any output): - Read these sections in `WORKFLOW_OPERATING_SYSTEM.md` first: - `## LLM execution contract` - `## Editor mode policy` - `## Global output contract` (including **Adaptive handoff** and **Mode selection rule**) - `## Cross-cutting workflow guardrails` - `## Project-level memory` - `## Evidence priority` - Read additional sections only when needed: - naming/path setup: `## Naming conventions`, `## Repository structure` - multi-repo schema: `## Multi-repo support (v1)` - Read the `commands/` directory command inventory to ensure routing recommendations are current. Required inputs: - target project identifier (`<client>__<project>`) or enough context to derive it from an active task folder under `projects/<client>__<project>/active/` - one or more research inputs, each being one of: - a URL to fetch and summarize (a GitHub or GitLab issue or PR URL triggers a deep comment-thread read, ADR-0086) - a topic o