architect

Translate a published spec into a design doc and interface stubs.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/chughtapan/safer-by-default --skill architect-chughtapan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/chughtapan/safer-by-default/tree/main/skills/architect
Command: npx skills add https://github.com/chughtapan/safer-by-default --skill architect-chughtapan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates a published spec into architecture-level design artifacts: a coherent design doc and a set of interface stubs that define the public surface without implementation details.

Core Features & Use Cases

  • Design doc generation from a published spec, including module names, responsibilities, data flow, and dependency considerations.
  • Public interface stubs that declare function signatures, typed error channels, and placeholder bodies throwing not implemented.
  • Traceability and alignment with the spec, with explicit open questions and decisions mapped back to the source document.

Quick Start

Provide a published spec URL and run the architect workflow to produce a design doc and interface stubs.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I generate a design doc from a software spec?

A design doc is generated by translating a published spec into architecture-level artifacts. The process decomposes the spec into modules, data flows, and dependencies, outputting a structured design document with explicit open questions mapped back to the source.

How do I create interface stubs from a design doc?

Creating interface stubs from a design doc involves defining the public surface without implementation details. The process outputs function signatures, typed error channels, and placeholder bodies throwing not implemented exceptions.

What is interface-only architecture output and when do I need it?

Interface-only architecture output defines public surfaces and typed errors without implementation logic. You need it when translating a formal spec into design artifacts, ensuring teams align on module responsibilities and data flows before coding begins.

Can I define typed error channels in interface stubs before implementation?

Yes, you can define typed error channels in interface stubs before implementation. The architecture process enforces interface-only outputs that explicitly declare function signatures and typed errors, returning placeholder bodies that throw not implemented.

Do I need a formal spec artifact to generate module responsibilities and data flows?

Yes, a formal spec artifact is required to generate module responsibilities and data flows. The architecture decomposition process depends on a published spec URL to map dependencies and produce coherent design artifacts accurately.