insights

Convert UI/UX review findings and external research into confirmed project requirements.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/ab300819/keel-workflow --skill insights-ab300819
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: insights
Source: https://github.com/ab300819/keel-workflow/tree/main/skills/insights
Command: npx skills add https://github.com/ab300819/keel-workflow --skill insights-ab300819

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Improvement ideas from UI/UX reviews, documentation research, competitor analysis, and internal feedback often get lost or are added to requirements without review. This Skill collects those suggestions, structures them with source traceability, and converts only user-confirmed items into numbered requirements. ## Core Features & Use Cases - Multi-Source Collection: Gathers suggestions from UI/UX reviews, document research, external references, and internal feedback with per-source handling guidance. - Interactive Confirmation: Uses AskUserQuestion for single or batch confirmation so no suggestion becomes a requirement without explicit user approval. - Classified Routing: Routes confirmed insights to requirements (F-XXX/AC-XXX), ADR design decisions, reusable patterns, or discards one-off observations, with an INS-numbered change log in 05-insights.md. - Use Case: After reviewing a login page, you list three UI problems; the Skill structures them as INS entries, confirms your selections, and appends traceable feature points to 01-requirements.md. ## Quick Start Run /insights and describe the improvement suggestions from your UI review, research, or external references to confirm and convert them into requirements.

Frequently Asked Questions about insights

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

FAQPage Schema
How do I turn UI/UX review findings into development requirements?

Run /insights and describe the issues found in your review. The Skill structures each finding as an INS entry with source, priority, and impact, then asks you to confirm which ones become numbered requirements (F-XXX) with acceptance criteria in 01-requirements.md.

How to extract improvement ideas from a reference article or URL?

Use /insights --url <url> to fetch and analyze the content, or /insights --file <path> for local review reports. The Skill extracts borrowable points as structured suggestions with source links, then asks you to confirm which to adopt.

Does every collected suggestion get added to the requirements document?

No. Suggestions are classified into four destinations: new requirements go to 01-requirements.md, decisions become ADR entries in the design doc, reusable lessons go to patterns docs, and one-off observations are discarded. Classification is confirmed with you, not decided automatically.

When should I use insights instead of feature or bugfix workflows?

Use insights when converting external findings or review suggestions into requirements. If you already have a clear feature to build, use the feature flow directly; for defects, use the bugfix flow. Insights is for the collection-and-confirmation stage before development.

What is the insights realign mode used for?

The --realign option scans 05-insights.md against the current ins.v1 spec and fills in missing template fields without adding new INS entries or changing business content. It is typically invoked through the pipeline realign orchestration.