Skip to content

rrrrrredy/research-toolkit / plugins/research-toolkit

research-toolkit

Flagged

Use for source-backed long-form research and writing in English or Chinese across fields, including revisions and continuation. Understand requirements, develop analysis through substantive research collaboration, and deliver a complete report after independent review, audit and acceptance.

FileKindSize
.codex-plugin/plugin.jsonconfig1.0 KB
.generated-files.jsonconfig6.3 KB
.mcp.jsonconfig158 B
LICENSEother1.0 KB
README.mdmarkdown3.4 KB
README.zh-CN.mdmarkdown3.0 KB
SKILL.mdskill md7.8 KB
SKILL.zh-CN.mdmarkdown6.5 KB
VERSIONother6 B
docs/compatibility.mdmarkdown3.8 KB
docs/compatibility.zh-CN.mdmarkdown3.2 KB
docs/delivery-verification.mdmarkdown19.2 KB
docs/delivery-verification.zh-CN.mdmarkdown16.3 KB
docs/review-completion.mdmarkdown18.0 KB
docs/review-completion.zh-CN.mdmarkdown14.7 KB
docs/usage-data.mdmarkdown15.4 KB
docs/usage-data.zh-CN.mdmarkdown13.9 KB
docs/usage-modes.mdmarkdown55.6 KB
docs/usage-modes.zh-CN.mdmarkdown48.6 KB
hooks/hooks.jsonconfig3.2 KB
mcp.jsonconfig253 B
plugin.jsonconfig1.1 KB
references/gotchas.mdmarkdown6.2 KB
references/gotchas.zh-CN.mdmarkdown3.6 KB
references/horizontal-vertical-analysis.mdmarkdown4.3 KB
references/horizontal-vertical-analysis.zh-CN.mdmarkdown3.2 KB
references/optional-analysis-lenses.mdmarkdown8.1 KB
references/optional-analysis-lenses.zh-CN.mdmarkdown6.1 KB
references/postmortem-lessons.mdmarkdown4.3 KB
references/postmortem-lessons.zh-CN.mdmarkdown3.5 KB
references/quality-gates.mdmarkdown5.7 KB
references/quality-gates.zh-CN.mdmarkdown4.5 KB
references/research-standard.mdmarkdown18.2 KB
references/research-standard.zh-CN.mdmarkdown13.7 KB
references/research-workflow.mdmarkdown25.5 KB
references/research-workflow.zh-CN.mdmarkdown19.9 KB
references/subagents-and-review-loop.mdmarkdown17.0 KB
references/subagents-and-review-loop.zh-CN.mdmarkdown13.4 KB
references/task-continuity.mdmarkdown6.9 KB
references/task-continuity.zh-CN.mdmarkdown5.3 KB
references/writing-style.mdmarkdown18.1 KB
references/writing-style.zh-CN.mdmarkdown14.9 KB
requirements-mcp.txtmarkdown11 B
scripts/agent_session.pyscript6.2 KB
scripts/check_delivery.pyscript44.6 KB
scripts/check_review_completion.pyscript28.5 KB
scripts/cli_agent_session.pyscript9.6 KB
scripts/codex_session.pyscript7.5 KB
scripts/extract_source_text.pyscript10.7 KB
scripts/host_review.pyscript78.4 KB
scripts/install_usage.pyscript9.7 KB
scripts/record_changes.pyscript13.7 KB
scripts/release_updates.pyscript9.8 KB
scripts/research_guidance.pyscript5.8 KB
scripts/research_host.pyscript52.4 KB
scripts/research_mcp.pyscript18.9 KB
scripts/research_records.pyscript28.5 KB
scripts/research_workflow.pyscript40.9 KB
scripts/review_process.pyscript5.2 KB
scripts/review_runner.pyscript20.2 KB
scripts/run_observation.pyscript7.7 KB
scripts/task_context.pyscript21.1 KB
scripts/task_lock.pyscript1.7 KB
scripts/task_reading.pyscript4.0 KB
scripts/task_storage.pyscript3.1 KB
scripts/usage_events.pyscript38.9 KB
scripts/usage_host.pyscript7.8 KB
scripts/usage_opencode.mjsscript3.1 KB

references/horizontal-vertical-analysis.md

View on GitHub
# Horizontal-Vertical Analysis

[English](horizontal-vertical-analysis.md) | [简体中文](horizontal-vertical-analysis.zh-CN.md)

Use this file only when the research task needs both time-depth and current-comparison. It is an optional method, not the default workflow of this skill.

## When To Use

Use horizontal-vertical analysis for:

- products and tools
- companies and organizations
- technical concepts or protocols
- market categories
- public figures or career trajectories

Use it when the reader needs to understand both:

- how the object became what it is
- how it compares with peers or substitutes now

Do not use it when the user only needs a short answer, a single-document summary, a narrow factual lookup, or a lightweight opinion.

## Core Structure

### 1. Vertical Analysis

Reconstruct the object's development over time.

Cover:

1. Origin: background, founding context, technical or market premise, initial problem, key people, and industry environment.
2. Birth point: first release, founding, first proposal, or first public form.
3. Evolution: key versions, financing, team changes, strategic shifts, architecture changes, user milestones, partnerships, acquisitions, crises, or controversies.
4. Decision logic: why major choices were made, what constraints existed, why one path was chosen over another.
5. Causal story: avoid a dry timeline; connect events into a readable account of cause, constraint, turning point, and consequence.

### 2. Horizontal Analysis

Compare the object with current peers, substitutes, or adjacent cases.

Determine coverage from the user's requirements and the question. Include every required object; choose additional peers or substitutes for the differences they help explain, without a fixed object count. If there is no direct competitor, examine the category, barriers, market, regulation or indirect substitutes.

Develop each comparison to the depth needed to answer the question. Uneven evidence should be disclosed, not used to silently omit required objects or fill gaps with invented symmetry.

Possible dimensions:

- technical route, method, or underlying logic
- product form, business model, organization structure
- target users and use cases
- strengths and weaknesses
- pricing, resource input, and scale
- user reception and real usage
- ecosystem position
- trend, opportunity, and risk

The comparison should not become a parameter table in prose. Explain what each peer has become, why users choose it, and where official positioning diverges from actual usage.

### 3. Intersection Judgment

The final section should combine both axes and produce new judgment, not summarize earlier sections.

Answer:

- Which historical choices explain today's position?
- Which strengths have historical roots?
- Which weaknesses were created by earlier good decisions?
- How do peers' different origins explain current differences?
- What is the most likely path from here?
- What are the upside and downside scenarios?

## Writing Guidance

- Prioritize readability over a mechanical consulting report.
- Use chronological explanation in the vertical section, but keep facts traceable.
- Use tables for comparable facts and prose to explain mechanisms, differences and trade-offs.
- Make judgments, but mark speculation clearly.
- Name the actor, action and mechanism behind abstract wording. Keep a term when it has a defined role in the evidence or the reader's field; use the [writing method](writing-style.md#process-language-cleanup) to edit by function rather than by a banned-word list.

## Depth And Length

Follow any agreed length constraint. Allocate detail according to the user's purpose, the questions that need explaining, complexity and available evidence. Historical reconstruction, current comparison and synthesis need not receive equal space or meet preset section lengths. Sparse evidence calls for an explicit limit, not filler or a shallower answer to the whole assignment.

## Output Pattern

Connect historical explanation, current comparison and their combined implications in the structure the question needs. They may form separate sections or appear within object-specific arguments. Use the agreed reference form; an appendix is included when requested or useful within the task. The method does not prescribe chapter names or require a separate block for every direction.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall