sp-research

Produce structured multi-source research findings with tagged claims and a recommendation.

23|2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/tta-lab/ttal-cli --skill sp-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sp-research
Source: https://github.com/tta-lab/ttal-cli/tree/main/skills/sp-research
Command: npx skills add https://github.com/tta-lab/ttal-cli --skill sp-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents anxiety-driven link gathering by structuring multi-source research into synthesis with a clear value stance and a recommendation the team can act on.

Core Features & Use Cases

  • Value-stanced research: forces a clear purpose before you read sources, so findings calibrate decisions or enable deliberate copying rather than vague aggregation.
  • Epistemic hygiene with claim tagging: distinguishes Verified, Interpretation, Speculation, and Unknown so the output remains auditable and correctable.
  • Decision-oriented deliverables: produces a structured findings document with Question, Findings, Trade-offs, Recommendation, Open Questions, and Sources, plus instructions for saving and annotating results for downstream pipeline handoff.

Quick Start

Use the sp-research skill to investigate how to design and validate an approach for your task, and end by producing a recommendation-backed findings document with clearly tagged claims and cited sources.

Frequently Asked Questions about sp-research

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

FAQPage Schema
How do I structure multi-source research into a decision-ready recommendation?

To produce a decision-ready recommendation, structure multi-source research by defining a clear value stance, tagging claims by verification status, and synthesizing findings into trade-offs, actionable recommendations, and open questions.

What is epistemic hygiene and how does claim tagging improve research synthesis?

Epistemic hygiene improves research synthesis by forcing you to tag claims as Verified, Interpretation, Speculation, or Unknown, ensuring the final output remains auditable, transparent in uncertainty, and correctable for downstream implementation.

How do I stop anxiety-driven link gathering and start producing actionable research findings?

You can stop anxiety-driven link gathering by forcing a clear purpose before reading sources, calibrating your investigation to compare approaches and extract portable design principles for a decision-oriented deliverable.

What format should a structured findings document follow for downstream pipeline handoff?

A structured findings document for pipeline handoff should include Question, Findings, Trade-offs, Recommendation, Open Questions, and Sources, accompanied by instructions for saving and annotating the results.

Can I use this approach to compare different approaches and extract portable design principles?

Yes, this approach is explicitly designed for task-driven scenarios where you must compare approaches, extract portable design principles, and deliver actionable synthesis for downstream implementation and team review.