create-architecture

Yes, the structured architecture workflow supports re-entrancy across sessions. It handles active epics and fallback paths to ensure repeatable processes and traceability throughout the architecture lifecycle.

To document software architecture decisions from an initial idea, this Skill uses structured Q&A to orchestrate goals and constraints, then generates architecture files like conventions and data models for traceable design.

The best way to establish architecture conventions for an active epic is through a re-entrant workflow that drives conventions.md and architecture files, ensuring decisions remain traceable across ongoing architecture workstreams.

You scaffold an architecture directory by completing the interactive Q&A process, which generates ready-to-write files for overview, conventions, data-model, and API surfaces aligned with your project strategy.

Yes, you can use this architecture workflow for standalone repositories. It includes fallback paths for non-epic projects, ensuring the structured decision-making process applies to any standalone repo.

Yes, the structured architecture workflow supports re-entrancy across sessions. It handles active epics and fallback paths to ensure repeatable processes and traceability throughout the architecture lifecycle.