collaborative-feature-definitionlisted

# Collaborative Feature Definition ## Purpose Turn an initial idea into an agreed, buildable Feature or Tech Feature without inventing missing intent or turning discovery into a one-shot questionnaire. The artefact is a living draft: each conversation round resolves the highest-impact gaps, updates the draft, and exposes what remains unknown. This skill stops at an accepted definition and, when required, its engineering-analysis companion. `feature-engineering` owns the subsequent independent readiness validation, planning, implementation, progress, and completion review. ## Classify the artefact - **Product Feature** — changes an outcome or behavior for a customer, user, operator, partner, or business process. Its value must be stated in those terms. Its definition is product-owned; engineering decisions are a separate, conditional stage. - **Tech Feature** — changes an engineering capability or system quality. Its value may be indirect, but must be measurable: risk/cost reduction, reliability, security, operability, performance, maintainability, developer productivity, or enablement of a named product outcome. If both apply, keep one parent objective and separate the product outcome from the enabling technical work. Do not hide a multi-feature initiative under one title. Identify both the artefact and the current stage. Read exactly one template for that stage: - For the product-owned definition of a Product Feature, read [Product Feature](references/produ