architecture-draft

Generate RFC or ADR documents from Product Requirement Documents.

6|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/vibbs/company-os --skill architecture-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-draft
Source: https://github.com/vibbs/company-os/tree/main/.claude/skills/architecture-draft
Command: npx skills add https://github.com/vibbs/company-os --skill architecture-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill bridges the gap between product requirements and technical implementation by generating detailed architectural design documents (RFCs/ADRs).

Core Features & Use Cases

  • Technical Design Generation: Translates approved PRDs into RFCs/ADRs, defining system boundaries, data models, API surfaces, and service layers.
  • Architectural Decision Making: Assists in making informed architectural choices and documenting them for future reference.
  • Use Case: After a PRD is approved for a new user authentication feature, use this Skill to draft an RFC that outlines the database schema, API endpoints, and security considerations for implementing it.

Quick Start

Use the architecture-draft skill to create an RFC for the new user profile feature based on the approved PRD.

Frequently Asked Questions about architecture-draft

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

FAQPage Schema
How do I translate a PRD into a technical design document?

To translate a PRD into a technical design, this Skill generates RFC or ADR documents that define system boundaries, data models, API specifications, and service layer logic based on your product requirements.

What is the best way to generate an Architecture Decision Record for a new feature?

Generating an Architecture Decision Record is best handled by translating an approved PRD to outline database schemas, API endpoints, and security considerations, ensuring informed architectural choices are documented for future reference.

Can I define system boundaries and data models from product requirements?

Yes, you can define system boundaries and data models directly from product requirements by generating a technical design that maps PRD specifications into detailed API surfaces and service layer logic.

Does this technical design generation handle cross-cutting concerns like multi-tenancy and observability?

Technical design generation explicitly addresses cross-cutting concerns like authentication, multi-tenancy, and observability, ensuring these architectural requirements are documented within the generated RFC or ADR.

How do I plan a migration strategy and check tech stack fitness during system design?

Planning a migration strategy and checking tech stack fitness are supported during system design, allowing you to validate architectural choices and document transition plans within the generated technical design documents.