add

Guide structured problem interviews and evidence collection to register viban issues.

5|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/happy-nut/claude-plugin-viban --skill add-happy-nut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add
Source: https://github.com/happy-nut/claude-plugin-viban/tree/main/skills/add
Command: npx skills add https://github.com/happy-nut/claude-plugin-viban --skill add-happy-nut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through a structured problem interview process to collect symptoms, context, and evidence, enabling consistent creation of viban issues.

Core Features & Use Cases

  • Interview-first workflow: prompts for structured information to uncover root causes before creating an issue.
  • Standardized issue body: produces a reproducible description with symptoms, steps, and context.
  • One-shot issue registration: allows registering a viban issue from collected data using a consistent format.

Quick Start

Start with an interview to collect problem details and then register a new viban issue with the collected data.

Frequently Asked Questions about add

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

FAQPage Schema
How do I collect problem details before registering a viban issue?

A structured problem interview workflow collects problem details by prompting for symptoms, context, and evidence, enabling consistent issue registration by uncovering root causes before ticketing.

What is a problem interview for issue reproduction?

A problem interview for issue reproduction is a formal workflow that extracts symptoms and context from users to build a standardized issue body with reproducible steps.

How do I create a standardized viban issue body with reproduction steps?

You create a standardized viban issue body by applying a formal workflow that consolidates collected interview data into a reproducible description containing symptoms, steps, and context.

Can I use a structured interview to identify root causes for engineering tickets?

Yes, you can use a structured interview to identify root causes for engineering tickets, as this workflow applies to engineering contexts requiring thorough context before ticketing.

Does the problem identification workflow work for both product management and engineering?

The problem identification workflow works for both product management and engineering contexts, applying structured interview prompts to gather thorough context before creating tickets.

What is the best way to ensure consistent viban issue registration?

The best way to ensure consistent viban issue registration is to follow a one-shot workflow that standardizes collected evidence into a reproducible description format.