feature-workflow

Automate a phase-ordered feature development workflow from planning to commit.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/devnogari/devnogari-claude-plugins --skill feature-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-workflow
Source: https://github.com/devnogari/devnogari-claude-plugins/tree/main/plugins/feature-workflow/skills/feature-workflow
Command: npx skills add https://github.com/devnogari/devnogari-claude-plugins --skill feature-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enforces a disciplined, phase-ordered approach to implementing new features, reducing drift and miscommunication by providing a guided workflow from planning to code review and commit.

Core Features & Use Cases

  • Structured multi-phase process with mandatory delegation to feature-dev for orchestration.
  • LSP-first, parallel subagents, and Ralph-loop-based reviews to maximize efficiency and quality.
  • Gate-driven progression that prevents skipping steps and ensures traceability across frontend, backend, or mobile projects.

Quick Start

Invoke the feature-workflow skill to begin a guided, phase-ordered development cycle. For example, /feature-workflow:feature-workflow "Add user settings page" and follow the prompts to plan, gate, implement, review, and commit.

Frequently Asked Questions about feature-workflow

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

FAQPage Schema
How do I automate a structured feature development workflow from planning to commit?

Automate feature development by invoking a guided workflow that enforces phase-ordered progression, LSP-first exploration, parallel subagents, and Ralph-loop code reviews from planning to commit.

Can I enforce TDD and code review phases when building new features across different stacks?

Yes, this workflow applies gate-driven progression across frontend, backend, and mobile stacks, enforcing TDD, phase-ordered steps, and Ralph-loop code reviews to prevent skipping critical development phases.

What is LSP-first exploration and how does it fit into a feature implementation workflow?

LSP-first exploration prioritizes Language Server Protocol queries for codebase analysis before implementation, fitting into a structured feature workflow by delegating exploration and coding tasks to parallel subagents.

Does feature-workflow work with my existing frontend, backend, or mobile project setup?

The workflow operates across major stacks including frontend, backend, and mobile projects, using gate-driven progression and subagent delegation to implement new features without requiring specific external dependencies.

How do I use parallel subagents for code review and implementation?

Parallel subagents are delegated implementation tasks during the feature workflow, while Ralph-loop code reviews ensure quality and traceability through mandatory, gate-driven review cycles before committing.

When should I avoid using a phase-enforced feature development workflow?

Avoid phase-enforced workflows for rapid prototyping or trivial fixes where strict gate-driven progression, LSP-first exploration, and mandatory code review loops would introduce unnecessary overhead.