feat

Plan and implement new features with exploration briefs and decision logs.

9|9|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/nullmastermind/viber-router --skill feat-nullmastermind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feat
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/feat
Command: npx skills add https://github.com/nullmastermind/viber-router --skill feat-nullmastermind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to align on feature scope, requirements, and success criteria, leading to scope creep and delayed delivery.

Core Features & Use Cases

  • Structured exploration: frame problems, gather requirements, and identify success metrics.
  • Decision artifacts: produce exploration briefs, options comparisons, and a minimal spec outline.
  • Collaboration workflows: synchronize with stakeholders through guardrails and documented decisions.

Quick Start

Plan and begin feature exploration by articulating scope, risks, and a minimal spec outline.

Frequently Asked Questions about feat

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

FAQPage Schema
How do I map feature requirements and prevent scope creep during discovery?

To map feature requirements and prevent scope creep, you must frame the problem, gather concrete requirements, and identify success metrics. This structured feature discovery process produces exploration briefs and a minimal spec outline to align stakeholders.

What is the best way to document feature decisions and evaluate implementation options?

The best way to document feature decisions is to maintain a decision log alongside options comparisons. Evaluating implementation options requires assessing risks and documenting concrete guardrails to ensure a clear execution path.

How do I scope feature work and create a minimal spec for development?

You scope feature work by exploring boundaries, mapping requirements, and framing the core problem. Creating a minimal spec requires enforcing concrete steps and guardrails, resulting in a documented execution path for implementation.

Can I use this approach for both feature design and implementation phases?

Yes, you can use this approach for both feature design and implementation phases. It applies across discovery, design, and implementation, covering problem framing, requirement mapping, risk assessment, and option evaluation.

Why do teams struggle to align on feature scope and success criteria?

Teams struggle to align on feature scope and success criteria because they lack structured exploration and documented decisions. Without a minimal spec and decision logs, misalignment leads to scope creep and delayed delivery.