propose-feature-requirements

Create feature requirement specifications using EARS notation.

5|12|Updated Nov 24, 2025

Search Tags:#planning #templates #requirements #EARS #feature-spec #propose

Ready to run

npx skills add https://github.com/cbgbt/bottlerocket-forest --skill propose-feature-requirements

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: propose-feature-requirements
Source: https://github.com/cbgbt/bottlerocket-forest/tree/main/skills/propose-feature-requirements
Command: npx skills add https://github.com/cbgbt/bottlerocket-forest --skill propose-feature-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of unclear feature requirements by enabling teams to create or update specifications using EARS notation.

Core Features & Use Cases

Template-driven drafting: Copy and customize a unified requirements template for a feature, ensuring consistent structure.
Guided workflow: Step-by-step checks from concept existence to finalized requirements, including optional planning artifacts.
Use Case: Given an approved feature concept, generate a complete requirements document including functional + non-functional requirements and appendices.

Quick Start

Use the propose-feature-requirements skill to create or update a feature requirements document for a given concept, such as NNNN-feature-name, following the documented process.

Frequently Asked Questions about propose-feature-requirements

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

FAQPage Schema

How do I write functional requirements using EARS notation?▼

EARS notation structures functional requirements using specific keywords to define conditions and system responses. This skill guides you through drafting these structured requirement statements, ensuring precise and unambiguous specifications for your feature concepts.

What is the best way to draft a feature specification from an approved concept?▼

Drafting a feature specification involves copying a unified template and populating overview, functional, non-functional, and appendix sections. This skill enforces a guided workflow to transform an approved concept into a complete, structured requirements document.

Can I generate non-functional requirements alongside functional ones for a feature?▼

Yes, generating non-functional requirements alongside functional ones is supported. The skill provides a structured template to specify both categories using EARS keywords, ensuring comprehensive coverage of system constraints and behaviors within the same document.

How do I structure a requirements document with EARS templates?▼

Structuring a requirements document requires defining a short ID prefix, populating an overview, specifying functional and non-functional requirements with EARS keywords, and organizing appendices. This skill automates that formatting to yield a consistent feature specification.

Do I need an approved feature concept before creating requirements?▼

Yes, an approved feature concept is a prerequisite. The skill's workflow begins with concept verification and idea-honing checks to ensure the foundational idea is solid before proceeding to template copying and structured requirement drafting.

Why use EARS notation for feature requirements instead of plain text?▼

Using EARS notation for feature requirements eliminates ambiguity found in plain text by enforcing keyword-driven syntax for conditions and responses. This skill applies that structured process to produce precise, testable specifications.