report-updater

Plans which investment report artifacts to regenerate when new events or earnings arrive.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When new earnings, guidance, M&A, or regulatory events occur, analysts need to know which parts of an existing investment research report must be refreshed without rewriting everything from scratch. This Skill produces a structured update plan that scopes the re-execution work. ## Core Features & Use Cases - Impact Scoping: Compares the existing report's baseline date against the new event and identifies which workspace artifacts (input, valuation, macro/sentiment, risk scenarios, draft, QA) are affected. - Re-execution Planning: Lists the commands and skills to rerun in order, and flags whether the Rating and Price Target need revalidation. - Use Case: After a company reports quarterly earnings with a tariff-related guidance change, invoke this Skill to write an update plan to ${ACTIVE_WORKSPACE}/00_input/update-plan.md specifying that valuation, risk scenarios, and the draft must be regenerated while long-term sections remain unchanged. ## Quick Start Update the existing CSTM report for the latest earnings event and write the re-execution plan to the workspace update-plan file.

Frequently Asked Questions about report-updater

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

FAQPage Schema
How do I update an existing investment research report after new earnings?▼

Provide the existing report path or company ticker plus the update scope (earnings, guidance, M&A, etc.). The Skill compares baseline dates and writes an update plan to ${ACTIVE_WORKSPACE}/00_input/update-plan.md listing which artifacts to regenerate.

What does the report update plan contain?▼

The plan identifies affected workspace directories among 00_input, 03_valuation, 05_macro_sentiment, 06_risk_scenario, 07_draft, and 09_qa, lists commands and skills to rerun in order, and flags whether Rating and Price Target need revalidation.

Does the update plan modify the final report directly?▼

No. The update-plan is an execution plan only, not the report change itself. Downstream commands and skills perform the actual regeneration based on the plan.

Which event types can trigger a report update?▼

Supported update scopes include earnings, guidance, M&A, regulation, litigation, new products, tariffs, orders, and supply chain events. Each scope determines which report sections are marked for re-execution.

When should I rewrite the full report instead of planning an update?▼

If the new event invalidates the core long-term thesis or most artifacts are affected, a full regeneration may be more efficient than incremental updates. The plan's affected-artifact list helps make that judgment.