feature-dev

Orchestrate multi-phase feature development with subagents and worktree isolation.

Updated Jul 2, 2026

Search Tags:#workflow #planning #development #implementation #verification #feature

Ready to run

npx skills add https://github.com/SamyakJhaveri/loam --skill feature-dev-samyakjhaveri

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-dev
Source: https://github.com/SamyakJhaveri/loam/tree/main/seed/.claude/skills/feature-dev
Command: npx skills add https://github.com/SamyakJhaveri/loam --skill feature-dev-samyakjhaveri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating feature development across teams and codebases without a repeatable, safe workflow leads to drift and delays. This Skill provides an end-to-end process from exploration to evaluation, ensuring consistent planning, implementation, and validation.

Core Features & Use Cases

Exploration & planning: orchestrate multiple subagents to map scope, dependencies, and risks before coding.
Guarded implementation: perform tasks in isolated work contexts with stepwise progress verification.
Verification & recording: run checks, summarize results, and record decisions for future reuse.

Quick Start

Describe the feature in the Arguments to initiate the plan phase and wait for user approval before execution.

Frequently Asked Questions about feature-dev

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

FAQPage Schema

What is the best way to plan and implement a non-trivial feature across a codebase?▼

Feature development requires an orchestrated workflow that spans exploration, specification, implementation, and verification. Using an end-to-end process with worktree isolation and subagents ensures consistent planning and safe validation before changes are applied.

How do I coordinate feature development without causing codebase drift?▼

You can prevent codebase drift by enforcing a multi-phase feature development workflow. This process requires user approval before execution, utilizing isolated work contexts and stepwise progress verification to maintain consistency across teams.

How does an automated feature workflow handle scope and dependency mapping?▼

Automated feature workflows handle scope and dependency mapping by orchestrating multiple subagents during the exploration phase. This allows you to map risks, dependencies, and scope thoroughly before any implementation begins.

Does feature development require manual approval before implementation starts?▼

Yes, guarded feature development requires explicit user approval before execution. After the plan phase generates a specification, you must approve it before the workflow proceeds to implementation and verification phases.

Can I use worktree isolation to safely verify feature implementation?▼

Yes, worktree isolation provides a safe context for guarded implementation and stepwise progress verification. This approach runs checks and summarizes results within an isolated environment, recording decisions for future reuse without risking your main branch.

What are the limitations of using a structured workflow for adding non-trivial features?▼

A structured feature development workflow requires completing distinct Explore, Spec, Implement, Verify, and Record phases. You must wait for user approval between planning and execution, which may introduce delays if immediate code changes are needed.