new-spec

Automate seven-step behavioral spec creation for noddde modules.

43|1|Updated Feb 19, 2024
One-click install
npx skills add https://github.com/dogganidhal/noddde --skill new-spec-dogganidhal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-spec
Source: https://github.com/dogganidhal/noddde/tree/main/.claude/skills/new-spec
Command: npx skills add https://github.com/dogganidhal/noddde --skill new-spec-dogganidhal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This internal procedure guides teams through a standardized process to create new behavioral specs for noddde modules, reducing ambiguity and setup time.

Core Features & Use Cases

  • Stepwise guidance from intent understanding to finalization, including template selection, dependency determination, and breaking-change analysis.
  • Reference to existing templates under specs/templates and a mirrored spec path convention for source and tests.
  • Supports collaboration by enforcing a consistent spec structure ready for review and testing.

Quick Start

Follow the 7-step process to generate a starting spec scaffold for a module.

Frequently Asked Questions about new-spec

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

FAQPage Schema
How do I create a behavioral spec for a new module?

Behavioral specs standardize module requirements by enforcing frontmatter, type contracts, behavioral guarantees, and breaking-change analysis. They reduce ambiguity and setup time by providing a consistent, test-ready structure for team review.

How do I generate a test-ready specification structure from a template?

Behavioral specs standardize module requirements by enforcing frontmatter, type contracts, behavioral guarantees, and breaking-change analysis. They reduce ambiguity and setup time by providing a consistent, test-ready structure for team review.

What is the best way to document breaking changes in a module specification?

Behavioral specs standardize module requirements by enforcing frontmatter, type contracts, behavioral guarantees, and breaking-change analysis. They reduce ambiguity and setup time by providing a consistent, test-ready structure for team review.

Does this spec generation process work for existing modules?

Behavioral specs standardize module requirements by enforcing frontmatter, type contracts, behavioral guarantees, and breaking-change analysis. They reduce ambiguity and setup time by providing a consistent, test-ready structure for team review.

What templates are needed to start writing a module behavioral spec?

Behavioral specs standardize module requirements by enforcing frontmatter, type contracts, behavioral guarantees, and breaking-change analysis. They reduce ambiguity and setup time by providing a consistent, test-ready structure for team review.

Why should I use a standardized specification process instead of writing docs manually?

Behavioral specs standardize module requirements by enforcing frontmatter, type contracts, behavioral guarantees, and breaking-change analysis. They reduce ambiguity and setup time by providing a consistent, test-ready structure for team review.