signals

Triage and enrich stakeholder feedback signals into validated roadmap chunks via MCP tools.

1|Updated Aug 15, 2026
One-click install
npx skills add https://github.com/AlrikOlson/think-and-ship --skill signals-alrikolson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signals
Source: https://github.com/AlrikOlson/think-and-ship/tree/main/crates/think-and-ship/skills/signals
Command: npx skills add https://github.com/AlrikOlson/think-and-ship --skill signals-alrikolson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Stakeholder feedback (questions, ideas, concerns, bugs) gets lost or forgotten between sessions, and agents either ignore it or nag users with unvalidated guesses. This Skill runs a disciplined signal loop: it pulls open signals, grounds them in the actual code, researches them against the outside world, and either promotes validated ones into the roadmap or dismisses refuted ones with an honest recorded reason. ## Core Features & Use Cases - Churn mode: Picks the oldest open signal, grounds it in the codebase with ministr, researches it with serpapi, records a durable enrichment with a confidence score, then promotes, dismisses, or defers it. - Surface mode: Raises at most one high-confidence, relevant, already-researched signal to the user at the right moment, honoring snooze, dismiss, or act-on-it reactions. - Auditable reasoning: Every enrichment links to a recorded think step and real sources, so a signal's verdict is traceable rather than ephemeral chat. - Use Case: A user types "/signals" mid-project; the Skill researches the oldest open feedback item, finds it is already addressed in the code, and dismisses it with the reason recorded — or validates it and creates a roadmap chunk for /roadmap to build. ## Quick Start Ask the agent to run /signals to churn on the oldest open stakeholder signal and report whether it should be promoted to the roadmap.

Frequently Asked Questions about signals

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

FAQPage Schema
How do I triage stakeholder feedback with an AI agent?▼

Run /signals with no arguments to churn the oldest open signal. The agent grounds it in the code with ministr, researches it with serpapi, records an enrichment with a confidence score, then promotes, dismisses, or defers it.

How do I capture a new feedback signal for a project?▼

Use /signals capture followed by the feedback text, which records a new signal via signal_capture. The signal enters the inbox as new and is picked up by a later churn pass.

What MCP tools does the signals workflow require?▼

It requires the think-and-ship MCP server for signal_* and think_* tools, plus ministr for code grounding and serpapi for web research. If ministr or serpapi is unavailable, enrichment proceeds with lower recorded confidence and the gap is flagged.

Why does signal_promote fail on a new signal?▼

A signal must reach the researched or surfaced state before promotion. Run a churn pass first so signal_research advances it, then signal_promote can convert it into a backlog roadmap chunk.

Does the signals skill implement the features it validates?▼

No. It only validates and promotes signals into roadmap chunks; actual implementation is handled by the /roadmap skill. It also does not reshape the roadmap, which is /roadmap-refresh's role.

Do signals persist between sessions?▼

Signals persist only when the server runs with THINK_AND_SHIP_PERSIST=true. Without it, native state is in-memory and signals vanish between sessions, which the skill flags when detected.