SDLC-decompose

Identify software components from design artifacts and create per-component directories.

2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/DYAI2025/Astro-Noctum --skill sdlc-decompose-dyai2025
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: SDLC-decompose
Source: https://github.com/DYAI2025/Astro-Noctum/tree/main/.claude/skills/SDLC-decompose
Command: npx skills add https://github.com/DYAI2025/Astro-Noctum --skill sdlc-decompose-dyai2025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify coherent software components from design artifacts and create per-component directories in the Code phase to enable modular development, clear ownership boundaries, and faster implementation.

Core Features & Use Cases

  • Component discovery: identify cohesive components from architecture, data-model, and API design documents.
  • Documentation scaffolding: generate per-component CLAUDE.component.md skeletons in 3-code/ for future implementation.
  • Workflow governance: preserve existing design artifacts and require explicit user approval before creating directories or files.

Quick Start

Approve the identified components to generate per-component directories and CLAUDE.component.md skeletons.

Frequently Asked Questions about SDLC-decompose

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

FAQPage Schema
How do I decompose software architecture design into modular code components?

Component decomposition identifies cohesive software components from architecture, data-model, and API design documents, then generates per-component directories with documentation skeletons to enable modular development and clear ownership boundaries.

What is component decomposition in the SDLC code phase?

Component decomposition applies explicit heuristics from architecture, data-model, and API design to determine boundaries, creating per-component directories and CLAUDE.component.md skeletons for structured implementation.

How do I scaffold per-component documentation from existing design artifacts?

Scaffolding per-component documentation involves generating CLAUDE.component.md skeletons in the 3-code/ directory and updating the CLAUDE.code.md overview, requiring explicit user approval before writing any files.

Can I generate component directories without overwriting existing design documents?

Existing design documents are preserved during component directory generation, and the workflow requires explicit user approval before creating any directories or files to ensure no artifacts are overwritten.

What happens when architecture design has ambiguous component boundaries?

When architecture design boundaries are ambiguous, the decomposition process surfaces these ambiguities for user review, ensuring components are only created after resolving unclear ownership or structural limits.