dev-specs

Name: dev-specs
Availability: InStock
Author: CodiHaus

Generate per-UC implementation specifications from BRD use cases.

Updated Jan 25, 2026

Search Tags:#documentation #specifications #generate #specs #use-cases #brd #scout

Ready to run

npx skills add https://github.com/codihaus/claude-skills --skill dev-specs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-specs
Source: https://github.com/codihaus/claude-skills/tree/main/.claude/skills/dev-specs
Command: npx skills add https://github.com/codihaus/claude-skills --skill dev-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BRD use cases are often informal or scattered; this skill converts them into formal, implementable specifications that guide engineering work and testing.

Core Features & Use Cases

Automated spec generation: Produce per-UC implementation plans with shared components and clear traceability to BRD criteria.
Context-aware integration: Leverages BRD use cases, scout outputs, and feature plans to ensure consistency and reduce rework.
Output artifacts: Generates UC folders, shared specs, tests, and an index for deployment planning.

Quick Start

Provide BRD use cases and feature context to generate complete specs in one run.

Frequently Asked Questions about dev-specs

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

FAQPage Schema

How do I generate implementation specifications from BRD use cases?▼

To generate implementation specifications from BRD use cases, provide the BRD and feature context to produce per-UC implementation plans, shared components, and traceability to BRD criteria.

What is the best way to turn informal BRD requirements into structured specs?▼

The best way to turn informal BRD requirements into structured specs is using context-aware integration that leverages BRD use cases and scout outputs to ensure consistency and reduce rework.

How do I create per-UC implementation plans with shared components?▼

You create per-UC implementation plans with shared components by processing BRD-driven features to produce formal specifications that guide engineering work and testing.

What output artifacts are generated when converting BRD use cases into specs?▼

Converting BRD use cases into specs generates UC folders, shared specs, tests, and an index for deployment planning.

Do I need scout outputs to generate specifications from a BRD?▼

Scout outputs are not strictly required but are leveraged for context-aware integration to ensure consistency and reduce rework when generating specifications from BRD use cases.