kn-spec

Generate feature specification documents with validation and review steps.

Updated Aug 27, 2026

Search Tags:#documentation #feature development #specification #product management #requirements gathering #sdd

Ready to run

npx skills add https://github.com/ducanhnguyen223/birthday --skill kn-spec-ducanhnguyen223

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kn-spec
Source: https://github.com/ducanhnguyen223/birthday/tree/main/.claude/skills/kn-spec
Command: npx skills add https://github.com/ducanhnguyen223/birthday --skill kn-spec-ducanhnguyen223

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of feature specification documents (SDDs) by guiding users through a structured process, ensuring all necessary components are included before development begins.

Core Features & Use Cases

Guided Spec Creation: Walks users through defining feature names, gathering requirements, and structuring the specification document.
Validation & Review: Includes a validation step to catch issues early and prompts for user review and approval.
Use Case: A product manager needs to document a new user authentication feature. They use this Skill to generate a comprehensive spec, including functional requirements, acceptance criteria, and scenarios, before handing it off to the engineering team.

Quick Start

Use the kn-spec skill to create a spec for the user-auth feature.

Frequently Asked Questions about kn-spec

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

FAQPage Schema

How do I create a feature specification document for product development?▼

To create a feature specification document, this Skill guides you through a Spec-Driven Development workflow to define feature names, gather detailed requirements, and structure sections like overview, acceptance criteria, scenarios, and technical notes.

What is Spec-Driven Development and when should I use it for requirements gathering?▼

Spec-Driven Development is a workflow that structures feature development by defining requirements, user stories, and edge cases before coding. You should use it to ensure all necessary specification components are validated and reviewed before engineering begins.

How do I structure product management requirements with user stories and acceptance criteria?▼

You structure product management requirements by using a guided process that prompts you for functional requirements, user stories, edge cases, and acceptance criteria, organizing them into a comprehensive specification document ready for technical notes.

Can I validate and review feature specifications before handing them to engineering?▼

Yes, you can validate and review feature specifications before handoff. The workflow includes a built-in validation step to catch issues early and prompts for your explicit review and approval before suggesting the next action for task creation.

What's the best way to document edge cases and scenarios for new product features?▼

The best way to document edge cases and scenarios is through a structured specification document that enforces dedicated sections for scenarios and acceptance criteria, ensuring engineering teams receive comprehensive coverage of functional requirements.

Does the kn-spec Skill require any external dependencies to generate specification documents?▼

No, the kn-spec Skill requires no external dependencies to generate specification documents. It operates independently using its internal scripts to facilitate the Spec-Driven Development workflow and produce the final structured output.