feature-spec-writer

Translates product analysis into structured feature specifications with Quick Spec and Full Spec templates.

Updated Aug 27, 2026

Search Tags:#markdown #requirements #spec #product #PM

Ready to run

npx skills add https://github.com/cncorp/arsenal --skill feature-spec-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-spec-writer
Source: https://github.com/cncorp/arsenal/tree/main/dot-claude/skills/feature-spec-writer
Command: npx skills add https://github.com/cncorp/arsenal --skill feature-spec-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates product insights into structured feature specifications, supporting fast handoffs to engineering and Linear ticket creation.

Core Features & Use Cases

Two spec formats: Quick Spec for fast ticket creation and Full Spec for complex features.
Open questions tracking: Maintains a list of questions and decisions.

Quick Start

Provide insights and decisions; the tool will generate a ready-to-use feature spec that can be copied into Linear.

Frequently Asked Questions about feature-spec-writer

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

FAQPage Schema

How do I convert product insights into a feature specification?▼

Feature specs translate research, user feedback, and product decisions into structured requirements. This Skill converts your analysis into actionable specs with problem statements, proposed solutions, success metrics, and technical considerations—ready to hand off to engineering or create Linear tickets.

What's the difference between a Quick Spec and a Full Spec?▼

Quick Spec generates lightweight specs for straightforward features, ideal for fast Linear ticket creation. Full Spec produces comprehensive documentation for complex features, including open questions, technical considerations, and out-of-scope items for detailed engineering handoffs.

Can I use feature specs to create Linear tickets directly?▼

Yes. The Skill outputs structured specifications formatted for direct copy into Linear. Both Quick Spec and Full Spec templates include all required fields—problem, solution, success metrics, requirements—so your tickets are complete and engineering-ready.

What should I include in my product insights before generating a spec?▼

Provide your analysis findings, product decisions, user needs, and any constraints. The Skill accepts raw insights and converts them into a formal specification framework with sections for problem definition, proposed solution, success metrics, requirements, and open questions.

How do I document technical considerations and out-of-scope items in a spec?▼

Full Spec templates include dedicated sections for technical considerations, open questions, and out-of-scope items. This structure ensures engineering teams understand trade-offs, dependencies, and boundaries before implementation begins.