architect-system

Transform product specifications into canonical architecture documents with stack, schema, APIs, and deployment.

14|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hungv47/meta-skills --skill architect-system-hungv47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-system
Source: https://github.com/hungv47/meta-skills/tree/main/forsvn-dev/skills/product/architect-system
Command: npx skills add https://github.com/hungv47/meta-skills --skill architect-system-hungv47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates product ideas and requirements into durable technical blueprints that specify stack decisions, database schema, API surface, deployment plan, and governance artifacts.

Core Features & Use Cases

  • Converts greenfield specs into a canonical architecture document that captures stack, schema, APIs, deployment, and security considerations.
  • Produces architecture/system-architecture.md along with rationale, trade-offs, and a clear artifact contract for downstream breakdown-tasks, review-work, and clean-code.
  • Ideal for major migrations, platform overhauls, or any initiative requiring a canonical system record.

Quick Start

Provide a product spec and run the architecture pass to generate the system architecture document and its supporting artifacts.

Frequently Asked Questions about architect-system

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

FAQPage Schema
How do I translate a product specification into a complete system architecture?

To translate a product specification into a system architecture, provide the spec to generate a canonical document covering tech stack decisions, database schema, API design, deployment plans, and governance artifacts with documented trade-offs.

What is included in a durable technical blueprint for a new software project?

A durable technical blueprint includes stack selections, database schema definitions, API surface design, deployment strategies, and security considerations, alongside rationale and constraints to guide downstream development tasks.

How do I document architecture trade-offs and rationale for a major platform refactor?

Document architecture trade-offs and rationale by generating a canonical system record at architecture/system-architecture.md, which captures constraints and decision logic to enable downstream task breakdown and code review.

Can I use this system design approach for both greenfield projects and legacy migrations?

Yes, you can use this system design approach for greenfield projects, legacy migrations, and major refactors to produce a unified architecture document specifying APIs, schema, and deployment governance.

What's the best way to generate a canonical architecture document for downstream development?

The best way to generate a canonical architecture document is to run an architecture pass on a product spec, producing an artifact contract that enables downstream breakdown-tasks, review-work, and clean-code implementation.

Do I need a product spec before generating a database schema and API design?

Yes, you need a product spec as input to generate the database schema and API design, as the system architecture document is derived directly from translating product requirements into technical blueprints.