architect-phase

Name: architect-phase
Availability: InStock
Author: MetaSaver

Convert user stories into architecture-annotated specifications with API endpoints and database models.

Updated Aug 23, 2026

Search Tags:#architecture #patterns #annotation

Ready to run

npx skills add https://github.com/metasaver/claude-marketplace --skill architect-phase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect-phase
Source: https://github.com/metasaver/claude-marketplace/tree/main/plugins/metasaver-core/skills/workflow-steps/architect-phase
Command: npx skills add https://github.com/metasaver/claude-marketplace --skill architect-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enriches user stories with architecture details, API endpoints, database models, and cross-cutting patterns.

Core Features & Use Cases

Architecture augmentation: Adds endpoints, models, components, and imports.
Pattern references: Documents Context7 references and reference files.
Reference discovery: Uses scope references and existing solutions for guidance.

Quick Start

Run architect-phase to enrich stories with architecture references and details.

Frequently Asked Questions about architect-phase

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

FAQPage Schema

How do I add architecture details to user stories?▼

Architecture annotation enriches user stories with API endpoints, database models, component names, and cross-cutting concerns. Run architect-phase after design completion to convert high-level stories into detailed specifications with implementation guidance, file paths, and import statements saved as enriched story artifacts.

What architecture patterns and references does the annotation process include?▼

The annotation process documents Context7 references, pattern implementations, and cross-references to reference repositories. It captures architectural decisions, import structures, and model definitions alongside endpoint specifications to provide complete implementation context.

Can I use architecture annotation before or after design phase completion?▼

Architecture annotation operates after design-phase completion. It assumes prior design decisions exist and enriches those outputs with implementation-level details—endpoints, models, components, and patterns—rather than establishing foundational architecture.

How do I discover which API endpoints and database models to add?▼

The annotation process uses scope references and existing solutions for guidance. It analyzes completed stories and applies reference repository patterns to generate appropriate endpoints, database models, and component structures aligned with established architectural conventions.

What output format does the architecture annotation generate?▼

Architecture-annotated specifications include enriched stories with embedded API endpoints, database model definitions, component names, file paths, import statements, and architecture notes. Output is saved as structured story artifacts with cross-references and pattern documentation.

Do I need existing reference repositories to use architecture annotation?▼

Reference repositories accelerate pattern discovery and consistency, but the annotation process can operate with scope references alone. Existing solutions guide endpoint and model generation, though custom definitions can substitute when standard references are unavailable.