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

clarify

Clarify ambiguous bug reports through a structured five-round question workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted engineering cycles by clarifying the exact goal, user flow, constraints, and acceptance criteria before any implementation starts.

Core Features & Use Cases

  • Adaptive 5-round Q&A: Asks one high-value question per round to reduce ambiguity while keeping the conversation structured.
  • Task Brief output: Produces a build-ready brief including task type, priority, user impact, scope, edge cases, affected areas, and open questions.
  • Optional Linear context loading: When you provide a Linear issue ID, it can fetch issue details, images, and comments to skip questions already answered.

Quick Start

Run the clarify skill with your bug description or feature idea so it can produce a Task Brief in exactly five rounds.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I turn vague bug reports into build-ready task briefs?▼

You can turn vague bug reports into build-ready task briefs by running a structured five-round adaptive question workflow that extracts scope, acceptance criteria, and edge cases.

How do I write acceptance criteria for incomplete feature requests?▼

Writing acceptance criteria for incomplete feature requests involves systematically identifying missing constraints, user flows, and edge cases through targeted questions to minimize ambiguity before development.

Can I use Linear issue IDs to load context for feature planning?▼

Yes, you can use optional Linear issue IDs like OPE-<number> to preload context such as issue details, images, and comments, allowing the system to adaptively skip questions already answered.

What information should a task brief include for software engineering?▼

A task brief for software engineering should include task type, priority, scope, user impact, acceptance criteria, edge cases, affected areas, non-functional requirements, testing approach, and open questions.

Does the structured clarification process support adaptive skipping?▼

Yes, the structured clarification process supports adaptive skipping, automatically omitting high-value questions during the five rounds if the required context is already preloaded or provided in the initial input.

Related Skills

Explore More Product & Management Skills→
glowingkittyglowingkitty
43

openmates:clarify

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

Community
Intermediate
bigeasyfreemanbigeasyfreeman
2

spec-to-tests

Convert Build Brief acceptance criteria into failing tests and reproducers.

Community
Intermediate
NoyoucringeNoyoucringe

linear-issue

Fetch and analyze a Linear issue with relations, comments, and attachments.

Community
Intermediate
WinnerWang971119WinnerWang971119

plan

Coordinate structured feature planning by gathering context and producing a formal spec.

Community
Advanced