architect-service

Generate service-level architecture documents from project PDR and contract constraints.

Updated Apr 26, 2026

Search Tags:#design #architecture #documentation #modules #specs #layering

Ready to run

npx skills add https://github.com/Dijjo10/sdd-opencode --skill architect-service

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect-service
Source: https://github.com/Dijjo10/sdd-opencode/tree/main/templates/service/.opencode/skills/architect-service
Command: npx skills add https://github.com/Dijjo10/sdd-opencode --skill architect-service

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams produce consistent, auditable service-level architecture artifacts that align with project-level constraints, ensuring clear boundaries, proper layering, and shared understanding across the team.

Core Features & Use Cases

Inherit project constraints: Reuse PDR and contract boundaries to define service scope.
Decompose architecture: Distill specs, architecture, and module boundaries into clear, separate documents.
Template-driven outputs: Generate .docs/specs.md, .docs/architecture/architecture.md, and optional .docs/architecture/modules/<name>.md to support deployment and review workflows.

Quick Start

Provide the project-level service boundary details to generate the service-level architecture documentation.

Frequently Asked Questions about architect-service

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

FAQPage Schema

How do I generate service-level architecture documentation from project constraints?▼

To generate service-level architecture documentation, you provide project-level service boundary details like the PDR and contracts. The skill inherits these constraints to produce structured specs, architecture layers, and module documents.

What is the best way to decompose a service into architecture layers and modules?▼

Decomposing a service into architecture layers and modules involves defining clear responsibilities, external dependencies, and cross-cutting concerns. This skill guides that decomposition by distilling boundaries into separate specs and module documents.

What files are needed to start documenting service architecture specs?▼

You need to provide project-level service boundary details, specifically the PDR and contracts, to start documenting service architecture. These inputs define the scope and constraints for the generated architecture files.

How does service architecture layering work with existing project contracts?▼

Service architecture layering works with existing project contracts by inheriting their boundaries to define the service scope. The skill ensures the generated architecture layers and specs align with these project-level constraints.

Can I output individual module documentation separately from the main architecture file?▼

Yes, you can output individual module documentation separately. The skill generates optional .docs/architecture/modules/<name>.md files alongside the main architecture document to support granular module reviews.