rs

Synthesize internal codebase archaeology with external market research for feature investigations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lucasmonstrox/mrtip --skill rs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rs
Source: https://github.com/lucasmonstrox/mrtip/tree/main/.claude/skills/rs
Command: npx skills add https://github.com/lucasmonstrox/mrtip --skill rs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of shallow or unverified feature research by enforcing a rigorous, multi-layered investigation process that combines internal codebase archaeology with external market verification.

Core Features & Use Cases

  • Internal Archaeology: Systematically maps feature impacts, code-as-action scripts, git history, and schema constraints to ensure decisions are grounded in the actual state of the repository.
  • External Research: Orchestrates fan-out research across multiple perspectives (market, regulatory, technical) with adversarial counter-review to ensure findings are robust and verified.
  • Use Case: When tasked with evaluating a new feature or market trend, use this skill to generate a comprehensive, audit-ready investigation document that includes code-level evidence, market trade-offs, and a clear implementation recommendation.

Quick Start

Use the rs skill to conduct a full investigation of the feature or theme identified by the provided ID or topic.

Frequently Asked Questions about rs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct deep feature investigation combining codebase archaeology with market research?

Deep feature investigation synthesizes internal codebase archaeology with external market research, mapping feature impacts, git history, and schema constraints to generate an audit-ready document with implementation recommendations.

What is codebase archaeology for architectural decision-making?

Codebase archaeology for architectural decision-making systematically maps feature impacts, code-as-action scripts, git history, and schema constraints to ground technical decisions in the actual state of the repository.

How do I verify external market research claims during technical discovery?

Verify external market research claims during technical discovery by orchestrating fan-out research across multiple perspectives and applying adversarial counter-review to ensure findings are robust and evidence-based.

Does this feature feasibility analysis require specific dependencies or environment setup?

Feature feasibility analysis requires no external dependencies, relying strictly on evidence-based reporting with citations from internal code, git history, and schema sources within your complex software projects.

What is the best way to evaluate a new feature against internal code constraints and market trends?

The best way to evaluate a new feature against internal code constraints and market trends is generating a comprehensive investigation document that includes code-level evidence, market trade-offs, and a clear implementation recommendation.

When should I not use adversarial verification for feature research?

You should not skip adversarial verification for feature research when external claims must be robust, as this multi-layered investigation process enforces strict evidence-based reporting and citation of internal sources.