add_feature

Append feature specifications with acceptance criteria to FEATURES.md.

Updated Feb 19, 2026

Search Tags:#automation #documentation #specification #backlog #feature #project-management #acceptance-criteria

Ready to run

npx skills add https://github.com/wesuuu/runbook --skill add-feature-wesuuu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add_feature
Source: https://github.com/wesuuu/runbook/tree/main/.agent/skills/add_feature
Command: npx skills add https://github.com/wesuuu/runbook --skill add-feature-wesuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating and maintaining feature specifications in the FEATURES.md backlog is repetitive and error-prone. This skill automates the process by drafting a complete spec with acceptance criteria and appending it to the backlog in a consistent format.

Core Features & Use Cases

Reads existing FEATURES.md to determine the next feature number and prevent duplicates.
Gathers details from the user to flesh out a full feature specification with acceptance criteria.
Appends the new entry to FEATURES.md and prints a succinct summary of what was added.
Enables teams to maintain a traceable, versioned backlog for new ideas.

Quick Start

Describe your feature idea, and I will append a detailed specification to FEATURES.md with acceptance criteria.

Frequently Asked Questions about add_feature

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

FAQPage Schema

How do I automate writing feature specifications to my backlog?▼

To automate feature specifications, you provide a feature idea and the tool drafts a complete spec with acceptance criteria, then appends it to FEATURES.md. This ensures consistent formatting and eliminates manual backlog entry errors.

What's the best way to generate acceptance criteria for a new feature?▼

Generating acceptance criteria for a new feature involves gathering details from the user and formatting them into a structured entry. The tool automatically derives the next feature number and writes these criteria directly into your FEATURES.md file.

How do I prevent duplicate entries when adding features to FEATURES.md?▼

To prevent duplicate entries in FEATURES.md, the tool reads the existing backlog to determine the next sequential feature number. It checks current entries before appending a new specification to maintain a traceable, versioned backlog.

Do I need an existing FEATURES.md file to write feature specs?▼

You do not need an existing FEATURES.md file to write feature specs. The tool can read an existing backlog or create a new FEATURES.md file, deriving the next feature number and appending your detailed specification accordingly.

Can I use this to maintain a versioned backlog for project management?▼

You can use this to maintain a versioned backlog for project management by appending structured feature entries to FEATURES.md. It enables teams to capture ideas as formal specs with acceptance criteria, ensuring traceability across project contexts.

What are the limitations of automating feature spec creation?▼

A limitation of automating feature spec creation is that it operates specifically within the FEATURES.md file format. It requires user interaction to gather details for the specification, meaning incomplete inputs may result in underdeveloped acceptance criteria.