define-feature

What problem does it solve?

This Skill helps product teams convert vague, half-formed feature ideas into a precise, unambiguous requirements table so engineering can write a technical spec and tests without further clarification. It focuses on clarifying the user problem, questioning assumptions, surfacing edge cases, and ensuring every requirement is testable.

Core Features & Use Cases

• Structured discovery: Restates the idea, identifies ambiguities, and asks focused questions that prioritise why before what.
• Scope, edge cases, and testability: Challenges unnecessary scope, enumerates error conditions and edge cases, and produces acceptance criteria that are directly testable.
• Draft persistence: Writes a draft requirements file to disk in product/{short-name}.md with a GUID and date so the new-feature workflow can proceed.
• Use Case: A product manager with a one-sentence idea uses this Skill to produce a requirements table that a developer can immediately convert into a technical spec and tests.

Quick Start

Use the define-feature skill by describing your rough idea in one or two sentences and asking it to produce a requirements table ready for the new-feature workflow.