architect

Convert a Product Requirements Document into a Software Design Document with architecture, data models, APIs, and tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/project-purupuru/world-purupuru --skill architect-project-purupuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/project-purupuru/world-purupuru/tree/main/.claude/skills/designing-architecture
Command: npx skills add https://github.com/project-purupuru/world-purupuru --skill architect-project-purupuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a Product Requirements Document (PRD) into a comprehensive Software Design Document (SDD) that serves as the definitive blueprint for engineering teams, reducing interpretation gaps and accelerating delivery.

Core Features & Use Cases

  • PRD-to-SDD conversion: Transforms requirements into architectural components, data models, API definitions, and testing strategies.
  • Traceability and justification: Links design decisions back to PRD requirements with explicit rationale and documentation of assumptions.
  • Sprint-ready artifacts: Produces grimoires/loa/sdd.md and outlines development phases to guide sprint planning and execution.

Quick Start

Provide grimoires/loa/prd.md as input and request grimoires/loa/sdd.md to be generated.

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, the Skill extracts functional and nonfunctional requirements from grimoires/loa/prd.md to generate grimoires/loa/sdd.md. This SDD includes architecture, data models, APIs, and development phases to guide sprint execution.

What is the best way to generate architecture and data models from product requirements?

Generating architecture and data models from product requirements involves transforming PRD inputs into structured SDD components. The Skill maps PRD specifications to define data models, API definitions, and architectural components, reducing interpretation gaps for engineering teams.

How does traceability work when creating an SDD from a PRD?

Traceability in SDD creation links design decisions directly back to PRD requirements with explicit rationale. The Skill documents assumptions, risks, and constraints to justify architectural choices, ensuring every component traces to a functional or nonfunctional requirement.

Do I need a specific PRD format to generate sprint-ready engineering documentation?

You need the grimoires/loa/prd.md file format to generate sprint-ready engineering documentation. The Skill parses this specific markdown file to extract requirements and output the comprehensive grimoires/loa/sdd.md blueprint for your engineering team.

Can I automate test strategy creation from product requirements documentation?

You can automate test strategy creation from product requirements documentation by processing the PRD through the Skill. It transforms PRD requirements into a comprehensive SDD that includes defined testing strategies alongside architecture and API definitions.

What should be included in a software design document to reduce engineering interpretation gaps?

A software design document should include architecture, data models, API definitions, testing strategies, and development phases to reduce interpretation gaps. The generated SDD also documents design rationales, assumptions, risks, and constraints to guide execution and future changes.