dev-feature

Organize multi-session feature development with structured folders and persistent documentation.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/eleva-labs/agentic-coding-templates --skill dev-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-feature
Source: https://github.com/eleva-labs/agentic-coding-templates/tree/main/.claude/skills/shared/dev-feature
Command: npx skills add https://github.com/eleva-labs/agentic-coding-templates --skill dev-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a repeatable workflow to manage complex, multi-session feature development with AI-assisted coordination, enabling continuity across sessions.

Core Features & Use Cases

  • Feature lifecycle orchestration: Research, design, planning, execution, validation, and handoff in a single, repeatable process.
  • Persistent documentation: AI agents maintain context across sessions via structured artifacts (INDEX.md, SESSION_HANDOFF.md, design/ and development/ docs).
  • Templates and standards: Enforces a consistent folder layout and templated documents to accelerate onboarding and ensure traceability.

Quick Start

  1. Create a feature folder under /docs/ignored/ with INDEX.md, SESSION_HANDOFF.md, and subfolders research/, design/, development/.
  2. Populate INDEX.md from templates and set up SESSION_HANDOFF.md for session handoffs.
  3. Begin with the Research phase by invoking the appropriate skill (e.g., /design-research) to start capturing context and requirements.

Frequently Asked Questions about dev-feature

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

FAQPage Schema
How do I maintain context across multiple AI sessions during feature development?

Multi-session feature development maintains context across AI sessions by using persistent documentation like INDEX.md and SESSION_HANDOFF.md. This structured approach captures research, design, and execution artifacts to ensure continuity.

What is the best way to orchestrate a long-running software feature with AI agents?

Orchestrating long-running software features with AI agents requires a structured workflow covering research, design, planning, execution, and validation. Template-driven artifacts enforce a consistent folder layout and clear execution order for traceability.

How do I structure documentation for complex refactors managed by AI?

Structuring documentation for complex refactors involves creating a feature folder with INDEX.md, SESSION_HANDOFF.md, and subfolders for research, design, and development. This layout maintains continuity and accelerates onboarding.

Does AI-driven workflow orchestration work for architecture changes?

AI-driven workflow orchestration works for architecture changes by applying a repeatable lifecycle process. It uses persistent documentation and templates to manage the complexity of long-running structural modifications across sessions.

What are the limitations of using template-driven artifacts for feature development?

Template-driven artifacts for feature development require strict adherence to a predefined folder layout and execution order. This approach suits long-running tasks but may add unnecessary overhead for trivial or single-session changes.