creating-feature-spec

Generate structured feature specification documents from feature definitions.

1|Updated Sep 22, 2025

Search Tags:#template #planning #architecture #specification #feature #product-management #spec-template

Ready to run

npx skills add https://github.com/pretodev/nice_app --skill creating-feature-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: creating-feature-spec
Source: https://github.com/pretodev/nice_app/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/pretodev/nice_app --skill creating-feature-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates clear, actionable feature specification documents from a user-provided feature definition, standardizing planning inputs for implementation teams.

Core Features & Use Cases

Analyze the user-provided feature definition to extract name, purpose, and high-level requirements.
Explore the codebase and project patterns (lib/shared, lib/features) to align the spec with existing architecture templates.
Produce a complete SPEC document using the SPEC_TEMPLATE.md structure, including sections for repository, commands, queries, views, and dependencies.
Provide a review-ready draft placed under specs/YYYYMMDD-feature-slug.md with clear assumptions and questions.

Quick Start

Provide your feature definition in the format Definição da feature [Nome da Feature] followed by the feature description to generate a structured SPEC document in specs/.

Frequently Asked Questions about creating-feature-spec

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

FAQPage Schema

How do I create a structured feature specification document from a feature definition?▼

To create a structured feature specification document, provide your feature description and the tool analyzes it to extract the name, purpose, and high-level requirements, then generates a review-ready draft placed under specs/YYYYMMDD-feature-slug.md.

Can I automatically align my feature spec with existing project architecture patterns?▼

Yes, you can align feature specs with existing architecture patterns because the tool explores the codebase, including lib/shared and lib/features directories, to match the generated specification with your current project templates.

What is the best way to standardize feature planning inputs for implementation teams?▼

The best way to standardize feature planning inputs is to generate formal spec documents using the SPEC_TEMPLATE.md structure, which includes predefined sections for repositories, commands, queries, views, and dependencies.

What format should I provide my feature definition in to generate a spec document?▼

You should provide your feature definition using the phrase Definição da feature [Nome da Feature] followed by the feature description to trigger the automated generation of a structured SPEC document in the specs/ directory.

Does the generated feature specification document include sections for queries and views?▼

Yes, the generated feature specification document includes sections for queries and views, along with repository, commands, and dependencies, by adhering to the complete SPEC_TEMPLATE.md structure.

What does the final feature specification draft include to help teams review the requirements?▼

The final feature specification draft includes clear assumptions and questions for the team to review, providing a standardized planning input ready for implementation teams to evaluate before building the feature.