define-feature

To turn rough feature ideas into testable requirements, you provide a brief concept and the skill restates the idea, identifies ambiguities, and asks focused questions to clarify the user problem before generating a structured requirements table.

Defining acceptance criteria and edge cases involves challenging unnecessary scope, enumerating error conditions, and producing directly testable criteria from your unstructured feature concept to ensure engineering has unambiguous instructions.

Yes, you can use this to create a requirements table for a developer. It is designed for product managers and cross-functional teams to refine feature concepts before technical specification and implementation.

The feature definition process persists your requirements draft by writing a file to disk with a GUID and date, ensuring the new-feature workflow can proceed with a saved record of the structured requirements.

To start brainstorming and refining feature specifications, you simply need to describe your rough idea in one or two sentences, which the skill then processes to produce a structured requirements table.

You should not use an automated feature definition approach if your idea is already a precise technical specification, as this skill focuses on clarifying vague, half-formed concepts and questioning assumptions before implementation.