factory-architect

Generate technical design documents with architecture, interfaces, data models, and acceptance criteria.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/JongHyunLee84/factory --skill factory-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-architect
Source: https://github.com/JongHyunLee84/factory/tree/main/skills/factory-architect
Command: npx skills add https://github.com/JongHyunLee84/factory --skill factory-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the critical need for a well-defined technical blueprint before development begins, ensuring alignment on architecture, interfaces, and acceptance criteria, and providing a clear GO/NO-GO decision point.

Core Features & Use Cases

  • Technical Design Generation: Creates comprehensive design documents outlining architecture, components, interfaces, and data models.
  • Acceptance Criteria Definition: Formulates clear, behavior-driven acceptance criteria using the ATDD pattern.
  • GO/NO-GO Gate: Facilitates a self-check and user approval process to validate the design before implementation.
  • Use Case: Before starting a new microservice, use this Skill to define its API contracts, data schema, and how its success will be measured, ensuring all stakeholders agree before coding starts.

Quick Start

Use the factory-architect skill to generate a technical design document for the new user authentication feature.

Frequently Asked Questions about factory-architect

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

FAQPage Schema
How do I generate a technical design document with architecture and acceptance criteria?

To generate a technical design document, you need to outline your software architecture, components, interfaces, and data models. Using ATDD patterns ensures testability, culminating in a GO/NO-GO gate for stakeholder approval before coding starts.

How do I define API contracts and data schema before starting a new microservice?

Defining API contracts and data schema requires a comprehensive technical blueprint outlining architecture and interfaces. This ensures all stakeholders agree on behavior-driven acceptance criteria and data models before implementation begins.

What's the best way to create a GO/NO-GO decision gate for software architecture approval?

The best way to create a GO/NO-GO decision gate is to formulate clear, behavior-driven acceptance criteria using the ATDD pattern. This facilitates a self-check and user approval process to validate the technical design before implementation.

What is ATDD pattern usage in technical design and software blueprints?

ATDD pattern usage in technical design ensures clarity and testability by formulating behavior-driven acceptance criteria. It validates the software blueprint through a GO/NO-GO gate, ensuring alignment on architecture and interfaces before development begins.

Can I use this approach to align stakeholders on interfaces and data models before coding starts?

Yes, you can align stakeholders by generating a technical design document that explicitly outlines architecture, components, interfaces, and data models. This well-defined software blueprint ensures agreement on success metrics before any coding starts.