feature

Orchestrate spec-driven feature development with automatic knowledge base discovery.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/roman-karpovich/ai-dev-team --skill feature-roman-karpovich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/roman-karpovich/ai-dev-team/tree/main/skills/feature
Command: npx skills add https://github.com/roman-karpovich/ai-dev-team --skill feature-roman-karpovich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Spec-driven feature development with KB-centric workflow streamlines end-to-end product delivery by anchoring decisions in a persistent knowledge base. It enables teams to discover KB automatically from sibling directories and manage full lifecycle: research, spec, implementation, and verification.

Core Features & Use Cases

  • Spec-driven workflow for new features, resuming work on existing specs, and tracking status across projects.
  • KB-discovery: automatically locate the knowledge base without manual configuration.
  • Cross-audit and verification steps to ensure quality before hand-off.

Quick Start

Start a new feature by saying '/feature new <description>' to initiate research, spec creation, implementation, and verification.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I manage spec-driven feature development from research to verification?

Spec-driven feature development orchestrates KB-backed research, spec creation, implementation, and verification across projects. It maintains persistent context to coordinate multi-step workflows and enforces a repeatable, audit-friendly lifecycle.

How do I automatically discover a knowledge base for feature workflow without manual configuration?

The feature workflow discovers the knowledge base automatically from sibling directories. This eliminates manual configuration by locating the KB context automatically to anchor spec creation and implementation decisions.

How do I start, continue, or check the status of a feature spec across projects?

Use the skill's start, continue, and status commands to initiate new feature research, resume work on existing specs, and track progress across projects. These commands coordinate the full lifecycle from research to verification.

What's the best way to ensure feature implementation passes cross-audit and verification before hand-off?

The feature workflow enforces cross-audit and verification steps to ensure quality before hand-off. It anchors decisions in a persistent knowledge base and maintains persistent context throughout the implementation lifecycle.

Can I use this spec-driven workflow for resuming work on existing feature specs?

Yes, the spec-driven workflow supports resuming work on existing specs and tracking status across projects. It maintains persistent context to coordinate multi-step workflows, allowing teams to continue feature development seamlessly.

Why does spec-driven feature development need a persistent knowledge base?

A persistent knowledge base anchors decisions throughout the feature development lifecycle, from research to verification. It enables automatic KB discovery from sibling directories and maintains context to coordinate multi-step workflows audit-friendly.