fabric-design

Convert backlog items into implementation specifications with data models and API signatures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill transforms vague backlog items into precise, actionable implementation specifications, preventing architectural inconsistencies and ensuring all edge cases are considered before coding begins.

Core Features & Use Cases

  • Detailed Design Specs: Generates comprehensive blueprints including data models, API contracts, integration flows, test cases, and risk assessments.
  • Prevents Rework: Bridges the gap between high-level requirements and low-level code, minimizing costly iterations.
  • Use Case: You have a backlog item to "Implement user profile update." This Skill will output the exact Pydantic models for the request/response, the API endpoint signature, pseudocode for validation logic, specific test cases (e.g., invalid email, password too short), and identify potential risks like data race conditions.

Quick Start

Use the fabric-design skill to create a detailed implementation specification for backlog item 'TASK-123'.

Frequently Asked Questions about fabric-design

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

FAQPage Schema
How do I convert backlog items into detailed implementation specifications?

To convert backlog items into implementation specifications, this Skill transforms vague tasks into precise blueprints covering data models, API contracts, integration flows, test cases, and risk assessments. It bridges high-level requirements and low-level code to minimize costly iterations.

What is the best way to design API signatures and data models before coding?

Designing API signatures and data models requires generating comprehensive blueprints that define request/response structures, endpoint signatures, validation pseudocode, and test cases. This prevents architectural inconsistencies and ensures edge cases are considered before coding begins.

How do I prevent architectural inconsistencies and vague hand-offs in software development?

Preventing architectural inconsistencies and vague hand-offs requires producing actionable implementation specifications with detailed data models, configuration, dependencies, and alternatives. This eliminates ambiguity and ensures deterministic LLM-driven development before implementation begins.

Does this specification approach support risk assessment and test case generation?

Yes, this specification approach supports risk assessment and test case generation by outputting detailed implementation blueprints. It identifies potential risks like data race conditions and defines specific test cases such as invalid email or password validation failures.

Can I use this tool to plan integration flows and configuration for Pydantic models?

Yes, you can use this tool to plan integration flows and configuration for Pydantic models. It generates exact Pydantic models for requests and responses, API endpoint signatures, and validation logic pseudocode from your backlog items.

When do I need a detailed design spec for my backlog items?

You need a detailed design spec for your backlog items when preventing rework and minimizing costly iterations. It bridges the gap between high-level requirements and low-level code, ensuring all edge cases are considered before coding begins.