spec

Decompose BRD documents into epics, stories, and machine-readable feature lists.

3|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill spec-cwijayasundara
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/cwijayasundara/claude_harness_eng_v5/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill spec-cwijayasundara

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of decomposing Business Requirements Documents (BRDs) into epics, stories, and feature lists, streamlining the Software Development Life Cycle (SDLC) and reducing manual effort.

Core Features & Use Cases

  • Automated Story Decomposition: Converts BRDs into structured, implementable units of work.
  • Feature Generation: Creates machine-readable feature lists for tracking and validation.
  • Use Case: Imagine you have a BRD for a new feature. Use this Skill to automatically generate epics, stories, and a feature list, saving time and ensuring consistency.

Quick Start

Run the spec skill with the path to your BRD file: /spec path/to/brd/file.md

Frequently Asked Questions about spec

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

FAQPage Schema
How do I automate story decomposition from a Business Requirements Document?

You can automate story decomposition by processing an approved BRD to automatically generate structured epics, stories, and machine-readable feature lists. This streamlines the Software Development Life Cycle by reducing manual effort and ensuring traceability.

What is BRD analysis for feature generation in SDLC automation?

BRD analysis for feature generation is the process of extracting requirements from a Business Requirements Document to create structured, implementable units of work. It produces machine-readable feature lists for tracking, validation, and SDLC traceability.

How do I generate epics and stories from a BRD file?

To generate epics and stories from a BRD file, run the skill with the file path to initiate structured analysis. The tool processes the approved document content and outputs decomposed work units and a feature list.

Do I need an approved BRD to generate machine-readable feature lists?

Yes, you need an approved BRD document to generate machine-readable feature lists. The skill relies on analyzing finalized business requirements to ensure the generated epics, stories, and features are valid and traceable.

What are the limitations of automating story decomposition from BRDs?

The primary limitation is its strict dependency on having an approved BRD document as input. Without a structured, finalized requirements document, the skill cannot accurately generate epics, stories, or machine-readable feature lists.