evidence-planner

Converts user research requests into question decompositions and evidence plans for analyst workflows.

Updated May 9, 2026
One-click install
npx skills add https://github.com/122yjs/invest_harness --skill evidence-planner-122yjs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evidence-planner
Source: https://github.com/122yjs/invest_harness/tree/main/plugins/vertical-plugins/invest-research/skills/evidence-planner
Command: npx skills add https://github.com/122yjs/invest_harness --skill evidence-planner-122yjs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Investment research requests often require evidence beyond company filings, such as market context, trade data, regulatory signals, and macro indicators. This Skill structures those open-ended requests into a formal question decomposition and evidence plan before any analyst fan-out begins, so downstream analysts know exactly which evidence types, source capabilities, and validation gates to apply. ## Core Features & Use Cases - Question Decomposition: Breaks a raw user request into entities, open-ended subjects, geographies, time horizons, claim types, and required evidence types, preserving the user's surface terms. - Evidence Planning: Maps each evidence type to source capability needs, signal primitives, and validation gates, including a mandatory narrative plausibility gate based on Damodaran's possibility, plausibility, and probability filters. - Role Slice Emission: Appends a machine-readable YAML block assigning required evidence types to six analyst roles (financial, fundamental, valuation, technical, macro-sentiment, risk-scenario). - Use Case: When a user asks to analyze a company with a tariff catalyst, run this Skill first to produce question-decomposition.md and evidence-plan.md in the workspace's 00_evidence folder, which downstream analyst skills then consume. ## Quick Start Ask the agent to run evidence planning on the current investment research request so it writes the question decomposition and evidence plan into the workspace evidence folder.

Frequently Asked Questions about evidence-planner

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

FAQPage Schema
How do I plan evidence requirements before running investment analyst agents?▼

Run the evidence planning step first to decompose the user request into entities, subjects, claim types, and required evidence types. It writes question-decomposition.md and evidence-plan.md to the workspace evidence folder, which downstream analyst skills read to scope their work.

What is a question decomposition in equity research workflows?▼

A question decomposition breaks a raw research request into entities, open-ended subjects, geographies, time horizons, investment claim types, and required evidence types. It preserves the user's surface terms and records mapping confidence for unfamiliar concepts.

How are validation gates applied to business narratives?▼

The plan must include a narrative_plausibility gate based on Damodaran's three filters: possibility (physically and commercially feasible), plausibility (consistent with historical precedent and economics), and probability (realistic versus market expectations already priced in).

Does evidence planning fetch market data or call external APIs?▼

No. The planning step is explicitly prohibited from fetching data, calling APIs, storing API keys, or making investment conclusions. It only designs the evidence plan, source capability needs, and validation gates for later execution stages.

What are role slices in an evidence plan?▼

Role slices are an inline YAML block appended to evidence-plan.md that assigns required evidence types to six analyst roles: financial, fundamental, valuation, technical, macro-sentiment, and risk-scenario. Each analyst skill reads only its own slice to plan evidence emission.

When should evidence planning not infer metrics from indirect signals?▼

The plan must not infer sales from search interest, market size from relative indexes, or company revenue from trade and procurement data alone. Such signals are recorded as evidence needs with explicit claim boundaries instead of direct conclusions.