Feature Specification Skill

Generate BR/US/AC feature specifications from codebases and designs with standardized IDs and dependency graphs.

4|1|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ruslan-korneev/claude-plugins --skill feature-specification-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Feature Specification Skill
Source: https://github.com/ruslan-korneev/claude-plugins/tree/main/plugins/tech-lead/skills/feature-specification
Command: npx skills add https://github.com/ruslan-korneev/claude-plugins --skill feature-specification-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Structured feature planning that converts scattered requirements, designs, and code insights into BR, US, and AC documents to improve alignment, traceability, and delivery quality.

Core Features & Use Cases

  • Generate Business Rules (BR-XXX-YYY), User Stories (US-XXX-YYY), and Acceptance Criteria (AC-XXX-YYY) from existing codebases or design notes.
  • Produce a complete feature template with dependencies, phased scope (core, workflow, lifecycle, analytics, integration, UI), and references for implementation.
  • Use Case: Given a project with multiple modules, produce a coherent feature specification document that maps to a dependency graph and a validation plan.

Quick Start

Create a new specification by describing the project goals and known components, and receive a ready-to-use BR/US/AC document.

Frequently Asked Questions about Feature Specification Skill

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

FAQPage Schema
How do I generate user stories and acceptance criteria from existing codebases?

You can generate user stories and acceptance criteria from codebases by providing project goals and known components to receive structured BR, US, and AC documents with standardized IDs. The skill analyzes existing modules and maps them to a dependency graph and validation plan.

What is the best way to structure feature specifications for a new project?

Structuring feature specifications is best achieved using a template-driven output that categorizes scope across core, workflow, lifecycle, analytics, integration, and UI phases. This enforces frontmatter compliance and generates complete feature templates with reference materials.

Can I convert scattered design notes into business rules and traceable requirements?

You can convert scattered design notes into business rules and traceable requirements by processing design inputs to produce standardized BR-XXX-YYY, US-XXX-YYY, and AC-XXX-YYY documents. This ensures alignment and traceability across your project delivery.

Does this feature specification tool support mapping dependencies across multiple modules?

This feature specification tool supports mapping dependencies across multiple modules by producing a coherent feature specification document that explicitly maps to a dependency graph and a validation plan. It ensures structured traceability across complex project architectures.

How do I plan phased feature scope covering UI, analytics, and integration from project ideas?

You plan phased feature scope from project ideas by describing your goals and receiving a ready-to-use document that organizes features across core, workflow, lifecycle, analytics, integration, and UI phases. It uses a standardized template to ensure comprehensive coverage.