design

Document architecture, interface contracts, and ADRs before coding.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill design-tasai-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/tasai-lab/fractal-dev-workflow/tree/main/skills/design
Command: npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill design-tasai-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before implementation, you need to solidify system architecture, interfaces, and test design to prevent late-stage churn and misalignment.

Core Features & Use Cases

  • Architecture design to define module boundaries and data models.
  • Interface design to contract APIs and integration points.
  • ADR-driven decision recording for traceability across phases.

Quick Start

Outline the architecture, interfaces, and tests upfront to establish a solid blueprint before coding.

Frequently Asked Questions about design

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

FAQPage Schema
How do I design software architecture before implementation to prevent rework?

To design software architecture before implementation, you should identify and lock module boundaries, interfaces, and test design upfront. This creates a solid blueprint that prevents late-stage churn and misalignment during coding.

What is an ADR and how does it help with task decomposition?

An ADR (Architecture Decision Record) is a structured design document that captures traceable decisions across phases. It helps with task decomposition by recording architectural choices, defining contracts, and ensuring alignment for parallel implementation.

How do I define interface contracts for parallel software development?

You define interface contracts by explicitly designing APIs and integration points before coding begins. This establishes strict phase gate checks and locked contracts, allowing multiple teams to validate and integrate their work in parallel.

When do I need to lock test design and architecture in a development workflow?

You need to lock test design and architecture before the coding phase begins. This structured design documentation phase satisfies requirements for traceable decision records and prevents late-stage churn in collaborative environments.

Does this architecture design approach work for multi-team collaborative development?

Yes, this architecture design approach is specifically built for collaborative software development. Multiple teams use the locked interfaces and architecture decisions to define contracts, enabling parallel implementation, validation, and seamless integration.