new-feature

Guide teams to design features with user stories and acceptance criteria.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/tulgardinc/vibe-check --skill new-feature-tulgardinc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-feature
Source: https://github.com/tulgardinc/vibe-check/tree/main/.claude/skills/new-feature
Command: npx skills add https://github.com/tulgardinc/vibe-check --skill new-feature-tulgardinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams design new features from the user's perspective by surfacing edge cases, assumptions, and acceptance criteria before engineering work begins.

Core Features & Use Cases

  • Interactive design sessions that prompt for context, constraints, and user needs to generate a complete feature spec.
  • Guided collection of vision, success metrics, user stories, and decision history to keep stakeholders aligned.
  • Reusable prompts and templates to facilitate rapid ideation across product, UX, and engineering discussions.

Quick Start

Describe your feature idea and request a complete, structured feature specification draft.

Frequently Asked Questions about new-feature

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

FAQPage Schema
How do I create a user-centered feature specification from an early-stage idea?

To create a user-centered feature specification, you need a structured process that gathers user-centric context, defines success criteria, and identifies edge cases. This approach generates a complete spec covering user stories, acceptance criteria, and constraints.

What should be included in a feature design document for product and engineering teams?

A feature design document should include user stories, acceptance criteria, constraints, vision, success metrics, and decision history. Capturing these elements keeps stakeholders aligned and ensures user needs are met before engineering begins.

How do I identify edge cases and assumptions before starting UX and engineering work?

To identify edge cases and assumptions before engineering work, use interactive design sessions that prompt for user needs and constraints. This guided collection surfaces hidden assumptions early, ensuring a more robust feature design.

Can I use this feature design process for rapid ideation across multiple product discussions?

Yes, you can use this feature design process for rapid ideation across product, UX, and engineering discussions. It provides reusable prompts and templates to facilitate quick ideation and generate structured specifications.

What is the best way to define clear success criteria for a new feature?

The best way to define clear success criteria for a new feature is through a guided collection of vision and metrics during early-stage design. This ensures the criteria are user-centric and aligned with stakeholder expectations.