architect

Convert brainstorm outcomes into user stories, architecture docs, and ADRs.

18|3|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/ondrej-svec/heart-of-gold-toolkit --skill architect-ondrej-svec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/ondrej-svec/heart-of-gold-toolkit/tree/main/plugins/deep-thought/skills/architect
Command: npx skills add https://github.com/ondrej-svec/heart-of-gold-toolkit --skill architect-ondrej-svec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts brainstorm outcomes into concrete, actionable documentation by generating structured user stories, architecture documentation, and ADRs to guide implementation.

Core Features & Use Cases

  • Generate standalone or pipeline-aware artifacts from a brainstorm: stories, architecture docs, and ADRs.
  • Provide a traceable design history with ADRs and a recommended file structure for implementation.
  • Supports triggers such as architect, stories, architecture, design, ADR, define stories, and write stories to integrate with existing workflows.

Quick Start

Provide your brainstorm context to generate an initial set of user stories, architecture docs, and ADRs.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I convert brainstorm outcomes into user stories and architecture docs?

To convert brainstorm outcomes into user stories and architecture docs, provide your brainstorm context to generate a ready-to-implement set of structured user stories, architecture documentation, and ADRs.

What is the best way to generate ADRs for system design?

Generating ADRs for system design involves creating a traceable design history from your brainstorm context, capturing dependencies, integration patterns, and architectural decisions to guide implementation.

How do I write user stories from a brainstorming session?

Writing user stories from a brainstorming session requires processing the outcomes into clearly formatted, actionable stories that define dependencies and recommended file structures for implementation.

Can I use pipeline-driven workflows to generate architecture documentation?

Yes, you can generate architecture documentation using pipeline-driven workflows by triggering the generation process with keywords like architecture, design, or ADR to produce standalone or pipeline-aware artifacts.

Does generating architecture docs require predefined integration patterns?

Generating architecture docs defines integration patterns and file structures as part of the output, deriving them from your brainstorm context rather than requiring predefined inputs.