software-design

Orchestrate multi-module software design sessions with domain modeling and TDD-ready issue generation.

1|2|Updated May 27, 2026
One-click install
npx skills add https://github.com/dividedby/skills --skill software-design-dividedby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-design
Source: https://github.com/dividedby/skills/tree/main/skills/engineering/software-design
Command: npx skills add https://github.com/dividedby/skills --skill software-design-dividedby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the ambiguity in complex software projects by transforming high-level PRDs and backlogs into structured, TDD-ready modules with clearly defined seams and testing strategies.

Core Features & Use Cases

  • Automated Design Orchestration: Coordinates domain modeling, codebase design, and adversarial review to ensure architectural integrity.
  • TDD-Ready Issue Generation: Rewrites backlog items into precise, observable behaviors with clear acceptance criteria and testing notes.
  • Use Case: When a new feature spans multiple backend modules and requires complex integration, this skill ensures the design is validated, documented, and ready for immediate implementation.

Quick Start

Run the software design skill to architect the current epic and generate TDD-ready issues for the project.

Frequently Asked Questions about software-design

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

FAQPage Schema
How do I design multi-module software architecture from a PRD and backlog?

To design multi-module software architecture, this Skill orchestrates domain modeling, codebase seam analysis, and TDD-ready issue generation to transform high-level PRDs and backlogs into structured, validated modules with clear testing boundaries.

How do I generate TDD-ready issues from a product backlog?

Generating TDD-ready issues involves rewriting backlog items into precise, observable behaviors with clear acceptance criteria and testing notes, ensuring complex feature development has clear architectural alignment and testing boundaries.

What is the best way to align domain modeling with codebase seams for new features?

Aligning domain modeling with codebase seams requires orchestrating automated design sessions that integrate adversarial review and architectural validation, ensuring multi-module integration is validated and documented before implementation.

Do I need an existing PRD and issue tracker to use automated software design?

Yes, automated software design requires existing PRD context, a populated issue tracker, and a defined domain vocabulary in CONTEXT.md to properly orchestrate multi-module design and TDD-ready issue generation.

When should I use multi-module software design orchestration for my project?

Use multi-module software design orchestration when a new feature spans multiple backend modules and requires complex integration, ensuring the design is validated, documented, and ready for immediate implementation with clear testing boundaries.