skills.rest
glowingkitty
glowingkittyCOMMUNITY
Explore all skills by this author →
GitHub

openmates:clarify

Run a 5-round Q&A to clarify bug reports and feature ideas into a Task Brief.

43|2|Updated Jan 25, 2024
Search Tags:#requirements#Linear#acceptance criteria#feature planning#product discovery#bug triage#task brief
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill openmates-clarify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openmates:clarify
Source: https://github.com/glowingkitty/OpenMates/tree/main/.claude/skills/clarify
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill openmates-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you fully understand a bug report or feature request by guiding a structured Q&A before any implementation starts, reducing rework and unclear requirements.

Core Features & Use Cases

  • Adaptive 5-round clarification: Asks exactly one high-value question per round, skipping topics already answered.
  • Context pre-loading for Linear issues: When given a Linear ID (e.g., OPE-123), it fetches issue details, related images, and comments to inform the questions.
  • Build-ready Task Brief output: Produces a structured brief including user impact, problem statement, expected/actual behavior (as applicable), scope, acceptance criteria, edge cases, affected areas, testing approach, and open questions.

Quick Start

Use openmates:clarify with your bug description, feature idea, or a Linear issue ID like OPE-123 to generate a complete Task Brief after 5 single-question rounds.

Frequently Asked Questions about openmates:clarify

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

FAQPage Schema
How do I turn a vague bug report into a build-ready task brief?▼

A structured 5-round Q&A process clarifies vague feature ideas by asking one high-value question per round to extract scope, acceptance criteria, edge cases, and testing approaches before coding begins.

Can I generate acceptance criteria directly from a Linear issue ID?▼

Yes, providing a Linear issue ID pre-loads issue details, related images, and comments to inform adaptive follow-up questions and generate a deterministic task brief with acceptance criteria.

How does adaptive question skipping work for feature planning requirements?▼

Adaptive skipping analyzes your initial feature planning input to identify already-resolved topics, ensuring the 5-round Q&A asks exactly one high-value question per round without redundant queries.

What is the best way to structure product discovery questions for new features?▼

A 5-round Q&A adaptively extracts the problem statement, expected behavior, scope, edge cases, and open questions into a comprehensive task brief for product discovery.

Does bug triage with structured Q&A eliminate scope ambiguity?▼

Bug triage with structured Q&A reduces scope ambiguity by deterministically generating affected areas, testing approaches, and acceptance criteria after five rounds of targeted clarification questions.

Related Skills

Explore More Product & Management Skills→
glowingkittyglowingkitty
43

openmates:reproduce-first

Require a failing end-to-end spec that reproduces a reported bug before writing fix code.

Community
Advanced
andregusman-raizandregusman-raiz
19

spec-writer

Generate standardized technical SPEC documents for features, issues, and refactors.

Community
Intermediate
OpenCovenOpenCoven
20

linear

Read Linear issue details, map project statuses, and draft issue updates.

Official
Intermediate
fcakyonfcakyon
1.0k

linear-usage

Standardize Linear issue creation with templates, labels, and triage workflows.

Community
Basic