analyzing-options
Analyzing different approaches for a task or problem with structured comparisons, effort…
Researching the product/feature in depth before any planning document is written: the product itself, technical approach, third-party integrations, prior art, and existing codebase grounding (file:line refs) via parallel repo/web/docs agents using firecrawl and exa. Gate 0 of
$ npx -y skills add LerianStudio/ring --skill researching-features --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/researching-featuresContext preview
The summary Claude sees to decide when to auto-load this skill.
Researching the product/feature in depth before any planning document is written: the product itself, technical approach, third-party integrations, prior art, and existing codebase grounding (file:line refs) via parallel repo/web/docs agents using firecrawl and exa. Gate 0 of
name: ring:researching-features description: "Researching the product/feature in depth before any planning document is written: the product itself, technical approach, third-party integrations, prior art, and existing codebase grounding (file:line refs) via parallel repo/web/docs agents using firecrawl and exa. Gate 0 of ring:using-pm-team (both tracks); runs before ring:writing-prds. Use before pre-dev planning a new feature or modification. Skip for trivial changes or when a recent research.md already exists."
**Runs before:** ring:writing-prds (Gate 1)
**Complementary:** ring:writing-prds, ring:writing-trds
Gathers deep technical/product research BEFORE writing planning documents, ensuring PRDs and TRDs are grounded in codebase reality, prior art, and authoritative technical sources.
**Scope is technical/product only.** Research covers: the product/feature itself (what it is, how comparable products solve it), technical approach, third-party integrations, prior art, and existing codebase patterns. **ZERO business content** — no market analysis, no personas, no user research, no go-to-market.
| Mode | When | Agent Priority | |------|------|----------------| | **greenfield** | New capability (no existing patterns) | Web research primary | | **modification** | Extending existing functionality | Codebase research primary | | **integration** | Connecting external systems | All agents equally weighted |
If unclear, ask: "Is this (1) Greenfield, (2) Modification, or (3) Integration?"
Single message, 3 Task calls:
| Agent | Focus | Mode Priority | |-------|-------|---------------| | `ring:repo-researcher` | Codebase patterns for [feature]; search docs/solutions/ knowledge base; return file:line refs | PRIMARY in modification | | `ring:web-researcher` | Technical approach, prior art, and best practices for [feature]; use firecrawl (search/scrape/crawl) + exa; return URLs | PRIMARY in greenfield | | `ring:docs-researcher` | Tech stack docs for [feature]; detect versions from manifests; firecrawl scrape/crawl of official docs + exa search; return version constraints | PRIMARY in integration |
Web research tooling is explicit: agents MUST use **firecrawl** (`firecrawl_search`, `firecrawl_scrape`, `firecrawl_crawl`) and **exa** for discovery and source retrieval — not memory.
If `TopologyConfig` provided (from command's topology discovery), persist in research.md frontmatter:
---
feature: {feature-name}
gate: 0
date: {YYYY-MM-DD}
research_mode: greenfield | modification | integration
agents_dispatched: 3
topology:
scope: fullstack | backend-only | frontend-only
structure: single-repo | monorepo | multi-repo
modules:
backend:
path: {path}
language: golang | typescript
frontend:
path: {path}
framework: nextjs | react | vue
doc_organization: unified | per-module
api_pattern: bff | none
---Compile all 3 agents' findings into `docs/pre-dev/{feature}/research.md`.
**Required sections:**
# Research: {Feature Name}
## Codebase Patterns
[From repo-researcher — existing patterns with file:line references]
## Technical Approach & Prior Art
[From web-researcher — how comparable products/projects solve this, candidate approaches, third-party integrations, with URLs]
## Framework Constraints
[From docs-researcher — version constraints, compatibility notes]
## Key Findings
[Top 5-10 insights that will inform PRD/TRD decisions]
## Risks & Unknowns
[Things that need more investigation before PRD/TRD]**File:** `docs/pre-dev/{feature}/research.md` with topology frontmatter (if provided)
After research.md complete: invoke `ring:writing-prds` (Gate 1).
Proven engineering practices, enforced through skills. Ring is a comprehensive skills library and workflow system for AI agents that transforms how AI assistants approach software development.
Repo: LerianStudio/ring
Analyzing different approaches for a task or problem with structured comparisons, effort…
Auditing a service's production readiness against Ring engineering standards across base…
Cleaning redundant and obvious comments following clean code principles while preserving…
Commit changes with scope allowlist enforcement, atomic grouping, GPG-signed conventional…
Creating a handoff document that captures session state (completed work, decisions, open…
Creating an isolated git worktree for parallel branch work: selects the directory by priority…