new-feature

Coordinate user-centered design sessions to produce engineer-ready feature specifications.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Capataina/agent-skills --skill new-feature-capataina
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-feature
Source: https://github.com/Capataina/agent-skills/tree/main/new-feature
Command: npx skills add https://github.com/Capataina/agent-skills --skill new-feature-capataina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interactive design sessions are time-consuming and subjective. This Skill helps teams capture user-centered requirements for a new feature, surface edge cases, challenge assumptions, and produce a concrete feature specification.

Core Features & Use Cases

  • Structured discovery process: prompts for context gathering from vision docs, memory items, and feature index.
  • Collaboration prompts: guide stakeholders through questions to surface requirements.
  • Output ready-to-use spec: yields a complete feature spec document for engineers.

Quick Start

Describe your feature idea to begin the design session and let the system gather context, ask focused questions, and draft a feature spec.

Frequently Asked Questions about new-feature

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

FAQPage Schema
How do I write user-centered feature specifications for product discovery?

You can elicit UX exploration requirements by applying rigorous questioning during a collaborative design session, gathering context from vision docs to articulate thorough feature needs.

What is the best way to elicit UX requirements and challenge assumptions for a new feature?

Yes, you can gather context from vision docs and memory items to inform the feature design session, ensuring the final specification captures thorough, user-centered requirements.

How do I run a feature design session that outputs an engineer-ready spec?

Feature specification sessions are useful for early-stage requirement elicitation and product discovery, helping teams move from subjective ideas to concrete, engineer-ready requirements.

Do I need vision docs to start a collaborative feature design session?

Run a feature design session by describing your feature idea to the system, letting it gather context, ask focused collaboration questions, and draft a complete specification document.

When should I use a structured design session for requirement elicitation?

To elicit UX requirements and challenge assumptions, coordinate a collaborative design session that prompts stakeholders with focused questions to surface edge cases and context.