feature

Create a feature branch and generate a Markdown design document with acceptance criteria and test plans.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/sjev/robodev --skill feature-sjev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/sjev/robodev/tree/main/skills/feature
Command: npx skills add https://github.com/sjev/robodev --skill feature-sjev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of creating and managing feature branches and their corresponding design specifications, ensuring consistency and adherence to architectural guidelines.

Core Features & Use Cases

  • Feature Branch Creation: Automatically creates or switches to a new Git branch for a specific feature.
  • Design Document Generation: Produces a structured Markdown document for feature design, including acceptance criteria, test plans, and more.
  • Use Case: When starting a new piece of work, use this Skill to set up your development environment by creating a dedicated branch and a template for your feature's design.

Quick Start

Create a new feature branch and design document for a feature named 'user authentication'.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I create a git feature branch and generate a design spec at the same time?

To create a git feature branch and design spec together, this Skill switches to a new `feat/<feature-name>` branch from `main` and automatically generates a structured Markdown design document at `docs/features/<feature-name>.md`.

What should a feature design document include for architectural consistency?

A feature design document should include architectural consistency guidelines, clear acceptance criteria, and a structured test plan. This Skill generates these sections automatically using predefined templates to ensure specification completeness.

Can I automatically switch to an existing feature branch instead of creating a new one?

Yes, you can switch to an existing feature branch. This Skill creates or switches to a `feat/<feature-name>` branch from the `main` branch, allowing you to resume work on an established feature without manual git checkout commands.

What's the best way to standardize feature development workflows across a team?

Standardizing feature development workflows requires consistent branch naming and design templates. This Skill enforces architectural consistency by standardizing the `feat/` branch naming convention and generating uniform design specification documents.

Do I need a docs directory before generating feature design documents?

Generating feature design documents places files at `docs/features/<feature-name>.md`. You should ensure your repository structure supports this path or allows the Skill to create the necessary directories for your Markdown specifications.

Why use a dedicated tool for feature branching instead of manual git commands?

Using a dedicated tool for feature branching eliminates manual git command errors and ensures design specs are never skipped. It enforces architectural consistency and automatically outlines test plans, streamlining the setup process.