architect

Extract functional and non-functional requirements from a PRD into a Software Design Document.

1|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/0xHoneyJar/loa-constructs --skill architect-0xhoneyjar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/0xHoneyJar/loa-constructs/tree/main/.claude/skills/designing-architecture
Command: npx skills add https://github.com/0xHoneyJar/loa-constructs --skill architect-0xhoneyjar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to translate a PRD into an actionable technical blueprint that engineers can implement. This skill converts a PRD into a comprehensive Software Design Document (SDD) that guides sprint planning and delivery.

Core Features & Use Cases

  • PRD intake & requirement extraction: Semantically analyzes the PRD to extract functional and non-functional requirements with traceability to PRD sections.
  • SDD generation & documentation: Produces a complete SDD at grimoires/loa/sdd.md covering system architecture, data models, APIs, security, testing, and deployment considerations.
  • Sprint-ready planning support: Aligns architecture with sprint goals, dependencies, risks, and milestones for engineering teams.
  • Use case: When a PRD is ready for architecture planning, run the architect skill to generate a sprint-ready SDD.

Quick Start

Convert the PRD at grimoires/loa/prd.md into a sprint-ready SDD at grimoires/loa/sdd.md.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I convert a PRD into a software design document for sprint planning?

To convert a PRD into a software design document, you extract functional and non-functional requirements to generate a comprehensive SDD covering system architecture, data models, APIs, and deployment considerations for sprint planning.

What is PRD-driven system architecture design?

PRD-driven system architecture design extracts requirements from a PRD and converts them into a complete Software Design Document, defining architecture, data models, APIs, and deployment considerations with explicit justifications.

Can I maintain PRD traceability in my generated design docs?

Yes, you can maintain PRD traceability by linking extracted functional and non-functional requirements directly to their corresponding PRD sections and explicit design decisions within the generated Software Design Document.

Does generating an SDD support sprint planning for engineering teams?

Generating an SDD supports sprint planning by aligning system architecture with sprint goals, dependencies, risks, and milestones, providing engineering teams with an actionable technical blueprint for delivery.

What's the best way to extract non-functional requirements from a PRD?

The best way to extract non-functional requirements from a PRD is through semantic analysis of the document, ensuring each requirement is traced back to its source section for accurate system architecture and security planning.

When do I need a complete Software Design Document for my project?

You need a complete Software Design Document when your PRD is ready for architecture planning and you must define system architecture, data models, APIs, security, testing, and deployment considerations to guide engineering delivery.