generating-modular-specs

Convert natural language requests into structured module specifications with dependency contracts.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/dallascrilley/dowser --skill generating-modular-specs-dallascrilley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generating-modular-specs
Source: https://github.com/dallascrilley/dowser/tree/main/skills/generating-modular-specs
Command: npx skills add https://github.com/dallascrilley/dowser --skill generating-modular-specs-dallascrilley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague feature requests and ambiguous requirements often lead to poorly scoped modules, unclear boundaries, and inconsistent implementations. This Skill translates natural language asks into precise, actionable module specifications with defined scope, dependencies, and documented decisions. ## Core Features & Use Cases - Module Intent Definition: Generates a stable snake_case module name, MODULE_ID, version, and implementation level (minimal, moderate, or high) from a natural language request. - Scope and Dependency Contracts: Defines explicit inclusion/exclusion boundaries and dependency contracts as module/contract path pairs. - Session Persistence: Writes a session.json file to ai_working/<module_name>/ with decision logs, confidence scores, and ask history using a provided JSON template. - Use Case: A user asks for "something that monitors API usage and alerts on anomalies." The Skill produces an api_usage_monitor specification with scope boundaries, alert system and metrics collector dependency contracts, and a persisted session record. ## Quick Start Ask the assistant to turn your feature request into a module specification, for example: "Create a module spec for a feedback summarizer that extracts themes and generates summary reports."

Frequently Asked Questions about generating-modular-specs

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

FAQPage Schema
How do I turn a vague feature request into a module specification?▼

Provide your natural language ask and the Skill extracts the core intent, assigns a snake_case module name and MODULE_ID, sets a version and implementation level, and defines scope boundaries. Ambiguities are resolved with up to five targeted clarifying questions before decisions are documented.

What is a module dependency contract in modular system design?▼

A dependency contract is a path reference to another module's contract file, expressed as {module, contract} pairs. The Skill only references these contract paths for cross-module behavior and never reads other specs or implementation code.

What implementation levels does the module specification support?▼

Three levels are supported: minimal for basic functionality, moderate for standard features with balanced complexity (the default), and high for full-featured production-ready implementations with testing and performance considerations.

Where is the module session data stored?▼

Session data is written to ai_working/<module_name>/session.json following the provided template. It records ask history, decisions, dependency contracts, a confidence score between 0.0 and 1.0, and timestamps.

When should I not use natural language module specification generation?▼

Avoid it when requirements are already fully specified in formal documents or when the system is not modular. The Skill is designed for converting ambiguous asks into module intents, not for refining existing detailed specifications.