feature

Coordinate end-to-end feature development with phase-driven governance and subagent delegation.

562|80|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/kdlbs/kandev --skill feature-kdlbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/kdlbs/kandev/tree/main/.agents/skills/feature
Command: npx skills add https://github.com/kdlbs/kandev --skill feature-kdlbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guided feature development provides a structured, governance-driven workflow that takes a feature from problem discovery through design, implementation with TDD, verification, and review.

Core Features & Use Cases

  • Phase-driven guidance: Understand, explore, design, implement with TDD, verify, and review.
  • Coordinated collaboration: Delegates tasks to subagents for each phase and maintains guardrails and approvals.
  • Reusable playbook: Use for new features or significant changes across projects.

Quick Start

Follow the four phases to begin a new feature: understand the problem, explore the codebase and architecture, design with explicit decisions, and implement with TDD, then verify and review.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I guide feature development end-to-end with TDD and design approvals?

You can guide feature development end-to-end by following a phase-driven workflow that covers problem discovery, codebase exploration, design with explicit approvals, and test-driven implementation to ensure continuous verification throughout the cycle.

What is a structured workflow for delivering new features and major changes?

A structured feature development workflow coordinates problem framing, architecture decisions, and test-driven implementation by delegating phase tasks to subagents while maintaining governance guardrails and enforcing explicit design approvals across the cycle.

Can I use this guided feature development process for team collaboration on architecture decisions?

Yes, this feature development process supports team collaboration by delegating tasks to subagents for each phase and maintaining guardrails, ensuring coordinated problem framing and explicit governance over architecture decisions.

What's the best way to manage a phase-driven workflow for test-driven implementation?

The best way to manage a phase-driven workflow for test-driven implementation is to enforce continuous verification across phases, delegating specific tasks to subagents while requiring explicit design approvals before proceeding to implementation.

Does guided feature development work for both new features and significant changes across projects?

Yes, guided feature development works as a reusable playbook for both new features and significant changes across projects, applying governance and a phase-driven workflow from problem discovery through final review.

Why do I need explicit design approvals during codebase exploration and architecture decisions?

You need explicit design approvals during architecture decisions to maintain governance and enforce the phase-driven workflow, ensuring continuous verification and proper task delegation before moving into test-driven implementation.