kn-spec

Create feature specification documents using Spec-Driven Development.

234|50|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/knowns-dev/knowns --skill kn-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kn-spec
Source: https://github.com/knowns-dev/knowns/tree/main/.agent/skills/kn-spec
Command: npx skills add https://github.com/knowns-dev/knowns --skill kn-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

kn-spec streamlines the creation of clear, testable feature specifications using Spec-Driven Development, reducing ambiguity and rework in the planning phase.

Core Features & Use Cases

  • SPEC FIRST: Define a complete spec for a feature before breaking it into tasks.
  • Review & Approve Loop: Facilitate stakeholder review and approval to keep everyone aligned.
  • SDD Workflow Integration: Generate and update spec documents that feed into planning and execution workflows.

Quick Start

To kick off a new spec, provide a feature name (e.g., "user-auth"), then follow the prompts to gather requirements, define acceptance criteria, and create a draft document in specs/. The system will announce the new spec and guide you through gathering details and producing a structured spec ready for review.

Frequently Asked Questions about kn-spec

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

FAQPage Schema
What is spec-driven development and how does it help with feature planning?

Spec-driven development (SDD) formalizes feature planning by capturing requirements, acceptance criteria, scenarios, and open questions in a single structured document before task breakdown. It reduces ambiguity and rework by enabling review and approval cycles prior to execution.

How do I create a feature specification document for a new feature?

To create a feature specification, provide a feature name like "user-auth" and follow prompts to gather requirements and define acceptance criteria. The system outputs a structured draft spec directly to the specs/ directory via MCP commands for immediate review.

What should be included in acceptance criteria and scenarios for a feature spec?

Acceptance criteria and scenarios in a feature spec should define testable conditions and specific use cases that validate the feature's behavior. The SDD workflow captures these alongside requirements and open questions to produce a structured draft ready for stakeholder approval.

Can I use spec-driven development to streamline stakeholder review and approval cycles?

Yes, spec-driven development facilitates stakeholder review and approval by generating a structured spec document that captures requirements, scenarios, and open questions. This keeps teams aligned and enables a clear review loop before moving from concept to task planning.

Does the generated specification document integrate with existing planning and execution workflows?

The generated specification document integrates with planning and execution workflows by outputting a structured draft to specs/ via MCP commands. This allows teams to move directly from concept definition and approval to downstream task planning.