feature

Automate feature implementation workflows from ideation through deployment with user gates.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/sukeun1997/claude-config --skill feature-sukeun1997
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/sukeun1997/claude-config/tree/main/skills/feature
Command: npx skills add https://github.com/sukeun1997/claude-config --skill feature-sukeun1997

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This pipeline orchestrates the entire lifecycle of new feature development, connecting brainstorming, planning, and execution with explicit user gates to ensure alignment and quality before each transition.

Core Features & Use Cases

  • 2-gate workflow: Move from ideation through Phase 0 (Tech Advisory if needed), Phase 1 (Brainstorming), Gate 1, Phase 2 (Planning), Gate 2, to Phase 3 (Execution).
  • Phased collaboration: Involves optional tech-advisor input, sub-skills for brainstorming and planning, and explicit user confirmations between phases.
  • Spec and plan artifacts: Generates vault-based spec and plan documents guiding implementation.

Quick Start

Describe the feature you want to implement to initiate Phase 0 of the 2-gate pipeline

Frequently Asked Questions about feature

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

FAQPage Schema
How do I automate end-to-end feature implementation workflows from ideation to deployment?

Automating end-to-end feature implementation workflows involves structured stages for brainstorming, planning, and execution with mandatory gate confirmations. A four-phase model with optional tech-advisor input ensures explicit user confirmations before progression.

What is the 2-gate feature pipeline process for product development?

The 2-gate feature pipeline process connects brainstorming, planning, and execution through explicit user gates to ensure alignment before transitions. It moves through Phase 0, Phase 1, Gate 1, Phase 2, Gate 2, to Phase 3.

How do you structure brainstorming and planning stages for new feature development?

Structuring brainstorming and planning stages for new feature development requires sub-skills for each phase and explicit user confirmations. Vault-based spec and plan artifacts are generated to guide implementation.

When do I need mandatory gate checks in a feature pipeline?

Mandatory gate checks in a feature pipeline are needed before transitioning between brainstorming, planning, and execution phases. They ensure alignment and quality by requiring explicit user confirmations before progression.

Does the feature workflow support tech-advisor input before planning?

The feature workflow supports tech-advisor input during Phase 0 before the brainstorming phase begins. This optional phase connects advisory input directly into the structured planning and execution pipeline.

How do I generate spec and plan artifacts for feature implementation?

Generating spec and plan artifacts for feature implementation is handled by vault-based document generation during the planning phase. These artifacts guide the execution stage following gate confirmations.